A broker restart loses messages the team believed were guaranteed, because the protocol never promised to keep them. We test five message queue protocols against the six properties every message-oriented middleware is judged on, and show where the wire ends and the broker begins.
TAG ARCHIVE
Data integration
What does a message-oriented middleware communication model actually guarantee?
A shipping service sits right next to billing on what everyone calls the same channel, and still never sees an order event that billing gets every time. The reason is the communication model underneath, not a bug in either service.
What message-oriented middleware is actually running under your queue?
A design review stalls when nobody can say why the queue fails the way it does under load. The tool was chosen; the message-oriented middleware underneath it, its communication model, protocol, and broker design, was not. This is the first of four pieces on that layer, closing on what Kafka solves across all three.