라우팅할 수 없는 메시지를 위한 대체 익스체인지

When a message reaches an exchange but matches no binding, RabbitMQ silently discards it (unless the publisher set the mandatory flag).

This silent loss is dangerous in production.

An Alternate Exchange (AE) is a fallback exchange. If the primary exchange cannot route a message, it forwards the message to its configured alternate exchange instead of dropping it.

You set the AE via the alternate-exchange argument when declaring the primary exchange.

The alternate exchange must also exist. A fanout AE is common because it broadcasts to whatever catch-all queue you bind.

Create a queue to collect the unroutable messages and bind it to the AE.

The flow is:

• Message published to orders
• No binding matches the routing key
• Message diverted to orders-ae
• Lands in the unrouted queue

The mandatory flag returns the unroutable message to the publisher via a basic.return.

An AE keeps it server-side in a queue. AE is better for centralized auditing; mandatory is better for immediate publisher-side handling.

An AE can itself have an alternate exchange, creating a fallback chain. Keep chains short to avoid confusing topology.

Do not confuse them:

• AE: triggered at publish time when no binding matches
• DLX: triggered after a message is in a queue and is rejected, expires, or overflows

• Always monitor the catch-all queue length
• Alert when it grows, since it signals routing bugs
• Process or inspect captured messages regularly

The user declaring an exchange with an alternate exchange needs read permission on the AE and write permission on the primary exchange, per RabbitMQ's authorization model.

An Alternate Exchange prevents silent message loss by capturing unroutable messages and forwarding them to a fallback exchange and catch-all queue.

Set it with the alternate-exchange argument, monitor the catch-all queue, and remember AE is publish-time while DLX is queue-time.