Don't Panic: Enterprise Integration Patterns

Enterprise Integration Patterns are a vocabulary for the awkward moment when independently built systems must exchange information or coordinate work. They are not a broker, framework, or large ceremonial appliance with a blinking dashboard. They are names for the choices hiding inside the wires, which is fortunate because unnamed choices tend to return later wearing a production incident badge.

Before this vocabulary, a team could connect sender to receiver directly, then connect the next sender to the next receiver, and eventually produce a landscape of private agreements. A message gives that agreement a unit of exchange. A command asks a receiver to act, a document carries a business record, and an event reports a fact that already happened. Those are not interchangeable labels. The receiver, the reply path, and the ownership rules change with the message's intent.

Next comes the channel, the logical route between endpoints. Point-to-point means one consumer handles a work item. Publish-subscribe means each interested subscriber receives a copy of a fact. A router chooses a destination, a splitter creates parts, and an aggregator brings related results back together. The terminology can sound like a box of spare plumbing. It earns its keep when a design review can ask which component owns routing instead of asking why three services have made different guesses.

The surprise is that delivery is not a footnote. A retry may happen after work was completed but before the response arrived. At-least-once delivery can therefore produce duplicates. An idempotent receiver handles the same work again without repeating its intended effect. Dead-letter channels, correlation identifiers, message history, traces, logs, and replay procedures are part of the flow, not the paperwork added after the flow has misbehaved in public.

Read the intro when the whole path needs a calm explanation. Use the slides to compare message intent, channels, routing, transformation, and endpoint roles. Keep the cheatsheet nearby when a named pattern is on the tip of the tongue. The practice reference turns the vocabulary into a review sequence, and the exercise asks you to design one complete order flow. After that, the reference links lead into concrete frameworks, where the patterns stop being nouns and start becoming decisions with consequences.