An anonymous queue lets one microservice receive its own copy of broadcast notifications without choosing or coordinating a queue name. RabbitMQ generates a unique name, while the shared exchange routes messages to each consumer’s private queue. section 5.8.7
Configure an anonymous queue by:
- Asserting the shared Viewed exchange as a fanout exchange. section 5.8.7
Receiving Viewed notifications
A history microservice creates its exclusive anonymous queue, binds it to the Viewed exchange, consumes each notification, stores the video path, and acknowledges the message. A recommendations microservice can independently use its own anonymous queue. section 5.8.7
