The real cost of ignoring queues and message brokers
This is cheap to get right at the start and expensive to retrofit. Nobody bills you for neglecting queues and message brokers. The cost shows up somewhere else.
Most systems fail at the seams rather than inside any one component. Budget a little time for it every quarter and it never becomes a project of its own.
Where the cost lands
- Time spent on work that should not have been necessary
- Enquiries that quietly never arrive
- Queues absorb spikes that would otherwise take a system down
- Rework, once the problem is finally visible
Every queue needs a dead letter destination and someone watching it. The teams that handle this well are rarely the ones with the biggest budgets. It rarely shows up as a line item, which is exactly why it slips.
Turning this into a decision
Ordering guarantees are weaker than most teams assume. Getting it slightly wrong is survivable. Ignoring it entirely is not. If two people in the business would answer this differently, that gap is the actual problem.
The short version
The right architecture for a team of three is the wrong one for a team of thirty, and vice versa. Three things worth confirming about queues and message brokers before you move on:
- Someone can say what the current setup is without going to look
- Ordering guarantees are weaker than most teams assume — and you know whether that is true here
- There is a way to tell whether the last change to this helped
None of this needs a rewrite. Most of it is a morning's work once someone decides to do it.