Back to Catalog
Microservices
Messaging & Events
Messaging
Services talk via async message channels — no direct calls, no tight coupling.
Intent & Description
Real-world Use Case
Order placed → message to “orders” topic on Kafka. Inventory Service, Shipping Service, and Email Service each consume independently. If Email Service is down, messages queue up — no lost events, no cascading failure.
Source
📌 TL;DR
Messaging = async fire-and-forget between services. Decouple, buffer, and scale. Trade simplicity for resilience.
Advantages
- Temporal decoupling — sender and receiver don’t need to be up simultaneously
- Natural load leveling via message queues
- Publisher doesn’t need to know its consumers
- Resilient to consumer failures — messages persist until consumed
Disadvantages
- Eventual consistency — consumers lag behind producers
- More complex debugging (no request/response trace)
- Broker becomes a critical piece of infrastructure
- Message ordering, exactly-once, and schema evolution all need explicit handling