This page is a guide to a vocabulary, and it does not teach a pattern. Gregor Hohpe and Bobby Woolf's book Enterprise Integration Patterns named the roles in systems that talk through messages, and on a Grid made for design patterns those names fill the palette's Enterprise Integration section, from the Pro plan up. The 24 below mostly have no article of their own, so each gets a plain line, enough to recognise the name.
One sketch keeps the lines concrete. A farm cooperative's weighbridge produces a grain receipt for each load, which travels over a shared message bus to billing, and billing invoices the member from it. Billing is offline from 22:00 to 02:00 while harvest trucks keep coming. Here is a first draft, with a named node for nearly everything.
Styles: how two systems exchange anything
File Transfer: one system writes a file and another picks it up later. A day's receipts exported for billing to import at 02:00 would be this style.Remote Procedure Invocation: one system calls a function on another and waits for the answer. The weighbridge calling billing's API for each load would be this style, and at 23:00 nobody is there to answer.
Channels: where messages travel
Publish-Subscribe has no separate node here, because Publisher, Subscriber and Event Bus already say it.
Point-to-Point Channel: each message goes to one receiver, even when several share the channel. Message Channel sets it against publish-subscribe.Datatype Channel: a channel kept to one message type, so a reader knows what will arrive. Agrain-receiptschannel carrying nothing else is one (Message Channel again).Message Bus: the shared backbone many applications plug into, with agreed message formats, so a new application connects to the bus and not to each of the others. A Message Broker, a separate process that stores and routes messages, is one thing a bus can run on.
The message itself: its kind and its metadata
Document Message: a message that hands over data and leaves the receiver to decide what to do with it, as the grain receipt does. Command, Document & Event Messages sets it against the other two intents.Message Sequence: an ordered set of messages that belong together, numbered so the receiver can tell each one's position and whether any is missing. A harvest-end statement too large for one message could go as part 1 of 40, 2 of 40, and so on.Message Expiration: a time after which a message counts as stale. A spot-price quote good until noon should not be acted on at 12:01, whatever delayed it.Format Indicator: a field naming the format or version of the message. When receipts gain a new field, billing can read"formatVersion": 2and know which parser to use.
Routing and transformation: where it goes, what it looks like
Dynamic Router: a router whose rules change while it runs, typically because destinations tell it what they will accept. A Content-Based Router picks the destination from each message's content, by rules its owner writes.Composed Message Processor: splits a message, sends each part to its own processing, and recombines the results into one message. One node for what Splitter, a router and Aggregator do in a row.Envelope Wrapper: wraps the payload in the headers a transport requires, and takes them off at the other end, so the payload need not know about the transport.Canonical Data Model: one shared shape for a kind of data, which each system translates to and from, in place of translating to every other system. Normalizer works through what it saves and what it costs.
Endpoints: where application code meets messaging
Messaging Mapper: code that turns domain objects into messages and back, so theGrainReceiptclass and the message format can change separately. Message Translator converts one message format into another, which is a different job.Transactional Client: a client that sends and receives inside a transaction; one local to the messaging system does not reach a database write (Transactional Client).Message Dispatcher: one reader on a channel that hands each message to a chosen handler. With Competing Consumers, the receivers take messages from the channel themselves.Selective Consumer: a consumer that tells the broker which messages it wants from a shared channel (Selective Consumer).Durable Subscriber: a subscriber whose messages are kept while it is offline and delivered when it returns, for as long as the messaging system retains them. That is billing from 22:00 to 02:00, given a subscription in place before 22:00 and retention longer than those four hours.
System management: running it and seeing inside
Control Bus: a channel that carries operational commands to the running components, such as pausing one (Control Bus).Message History: a list, carried with the message, of the components it has passed through. It answers where this one message has been; following work across services in general is Distributed tracing.Message Store: a durable record of messages, for audit or replay. The draft's audit store is one. A Wire Tap is one way to get copies out of a channel; the store is where they stay.Smart Proxy: sits in front of a service, keeps each request's Return Address, puts its own in place of it, and forwards the reply to the right caller.Test Message: a marked probe sent through the live flow and checked at the far end. An hourly test receipt shows the route works while no trucks are arriving, and billing has to recognise it and not invoice it.Channel Purger: removes unwanted messages from a channel, such as test messages left behind before a go-live. A purged message never reaches its receiver.
When a named node earns its place
Placing one of these nodes is a claim about how the system behaves. So the test is a swap: replace the node with a plain role and a good name, as Pattern building blocks (generic roles) describes, and see whether anything true goes missing. If nothing does, the named node was clutter, as is any node for a role an existing node already covers. If the design depends on what disappeared, the node stays. A detail the design does not turn on fits on an edge label: "expires at noon" says as much as a Message Expiration node, unless expiry is what the diagram is about.
Practise the decision in the Messaging Endpoints & Broker Challenge. Its palette offers a Messaging Bridge, a Service Activator and a Return Address the brief does not name: ask of each what would be untrue without it. None of the 24 is in any Challenge's palette, so this is practice on their neighbours, and drawing the cooperative on a blank Grid is an optional extra.
The sketch, one node lighter
A Dynamic Router says its rules change while it runs. Receipts have one destination, billing, and nothing sends the router new rules, so the node was claiming something untrue. Take it out.
Billing is the Durable Subscriber node. Receipts still take the same route to it, and the audit copy still exists.
Now run the same swap on Billing: replace its Durable Subscriber node with a plain Subscriber of the same name. One fact has gone: that a receipt issued at 23:00 is waiting for billing when it comes back at 02:00. You could write the answer on the edge, but the sketch turns on that window, so this node stays.