Message Broker
ELI5 — The Vibe Check
A Message Broker is the post office of your microservices world. Services hand messages to the broker, and the broker figures out how to route and deliver them to the right services. Nobody talks directly — everything goes through the broker. Kafka, RabbitMQ, and AWS SNS are message brokers.
Real Talk
A Message Broker is infrastructure middleware that translates messages between messaging protocols and routes them between producers and consumers. It provides features like message routing, transformation, persistence, and delivery guarantees. Differs from a simple queue by supporting complex routing patterns.
When You'll Hear This
"Kafka is our message broker for all inter-service communication." / "The broker handles routing so services don't need to know each other's addresses."
Related Terms
Event-Driven Architecture
Event-Driven Architecture is like a gossip network. When something happens (order placed!), it broadcasts the news.
Message Queue
A Message Queue is a waiting room for tasks. Producers drop tasks in the queue, consumers pick them up and process them one at a time.
Pub/Sub (Pub/Sub)
Pub/Sub is like a newspaper service. Publishers write articles and drop them off.
Saga Pattern
The saga pattern is how you handle transactions that span multiple services. In a monolith, you'd wrap everything in one database transaction.