AMQP Message Routing Performance

AMQP Message Routing Performance

animation
amqp
protocols
messaging
Try Change number of bindings in exchange to 200.
Observe Watch Routing Time, Memory Overhead, CPU Load, and Cores Needed with 200 bindings.
Explain Explain why 200 bindings increase routing time when pattern match time per binding stays at 10 μs.

Technical boundaries. Each binding costs the entered time, and each queue copy includes 80 B metadata. Cores Needed is a routing-only CPU equivalent; broker memory use varies.

NoteInteractive Calculator: AMQP Message Routing Performance
TipBroker Bex, Messaging and broker domain expertCheckpoint: Message Routing Flow

You now know:

  • Producers publish to exchanges, not directly to application-owned queues.
  • The broker evaluates bindings, then copies the message only into matching queues.
  • The default example shows a 100-binding exchange, 3 matching queues, a 200-byte payload, and 4,800 messages per second, so routing cost is a design input rather than a hidden detail.

Follow One Message Through the Routing Parts

Give one message an identity, route it to two intended consumers, change one binding, repeat it, and restart a consumer. Record the exchange, queue, route key, receiver, and final state. A live connection does not prove correct routing.

Back to the chapter