Show Notes
Messaging systems are everywhere in modern software, yet one fundamental question rarely gets a straight answer: does control live in the broker, or in the services that use it? This episode of
Automatic works through the architecture of message brokers — exploring how responsibility is actually divided, where things go wrong, and what well-designed systems get right. It draws on
the source article on message broker control vs. coordination to give teams a sharper mental model for building with brokers intentionally.
Here's what the episode covers:
- Control vs. coordination: The broker owns how messages move; services own what those messages mean — and confusing the two is where architectures quietly unravel.
- Edges matter most: Producers shape message frequency and format; consumers govern back pressure and idempotency. The broker can surface symptoms of poor judgment at the edges, but it can't fix them.
- The temptation of broker features: When teams push business logic into routing rules or stateful broker filters, what feels like a shortcut becomes a maintenance maze — keeping the broker focused on transport protects long-term clarity.
- Message contracts as the real lever: A stable, well-versioned schema is more powerful than any broker capability. Additive changes, schema registries, and disciplined review processes reduce the broker to a fast, reliable pipe.
- Delivery guarantees and ordering myths: At-least-once delivery with idempotent consumers is the most practical foundation; chasing global ordering or exactly-once semantics often shifts hidden complexity rather than eliminating it.
- Governance, observability, and ownership: Topic naming conventions, lag dashboards, correlation identifiers, and clear stewardship aren't bureaucracy — they're the feedback loops that make control feel like confidence rather than guesswork.
The episode closes with a straightforward verdict: messaging systems run on shared custody. Brokers set the rails; services decide where to go and what to carry. When that boundary is clear — backed by strong contracts, idempotent consumers, and honest observability — teams ship faster and sleep better. For more from the show, check out the episode
Why Autonomous AI Agents Need On-Prem Isolation, which explores another dimension of infrastructure control in automated systems.
What is Automatic?
Agentic AI and automation from the perspective of whoever has to maintain it in six months. Where an agent genuinely belongs in a process, where a plain script is enough, how to design a handoff to a human, and what breaks quietly at scale.
Each episode takes one automation decision and reasons it through end to end — including the maintenance burden, the failure modes and the honest question of whether the process should exist at all. Written for operators and technical leads, deliberately free of hype. Five or six minutes an episode.
Topics include where an agent belongs versus a plain script, designing human handoffs, error handling and observability, maintenance burden, process mapping before automation, measuring what a workflow saves, and knowing when a process should be deleted instead.
Produced by Automatic.co, agentic AI and automation consulting. Full details, services and further reading at https://automatic.co