Don't Panic: Messaging Fundamentals

Messaging is how one component leaves a note for another component without standing in the corridor until it is read. A producer sends a message to a channel or broker. A consumer later receives it and applies an effect. This is useful when intake and processing run at different safe rates, which is a polite way of saying that systems rarely agree on when to be busy.

The important split is between a queue and a topic. A queue gives each work item to one consumer, so competing consumers can share the load. A topic gives every subscription its own copy, so independent consumers can react to the same event. The words are compact; the consequences are not. Pick the shape according to who must act, not according to which label looks more architectural.

A message is also an API. It needs an owner, fields, compatibility rules, identity, correlation, version, expiry, and a data classification. This is the surprise: moving data asynchronously does not make the agreement less strict. It removes the helpful moment when two services can glare at each other over a failed request.

Delivery adds another distinction. At-most-once delivery can lose a message. At-least-once delivery can repeat one. An idempotency key lets a consumer recognize repeated work, so a duplicate delivery does not duplicate an external effect. A successful send therefore proves that the message entered the path, not that the final effect happened. The broker has done its part. The difficult bit has merely acquired a timestamp.

Failures need a route of their own. Limit retries, move persistent failures to a dead-letter path, inspect the cause, then replay or discard deliberately. Queue depth and age show backlog, but neither manufactures consumer capacity. Correlation identifiers, attempt counts, and processing results make the path traceable when the inevitable interesting failure arrives.

Read the intro for the complete component and failure model. Use the slides to compare delivery and distribution shapes. Keep the cheatsheet nearby when choosing contract fields and operational signals. The practice reference and exercise make the route visible in a local broker, which is much calmer than discovering it first in a production incident.