When we are configuring a RabbitMQ instance one thing that we cannot forget to consider is that, in practice, the consumers of the queues may not be able to process some notifications or even the queue itself may reject messages due to some events. In that case, we must implement Dead Letter Exchanges, so it is possible to keep those messages and reprocess them some other time.
In this article, I intend to explain when to use Dead Letter Exchanges (DLXs), how to configure it at RabbitMQ and how a .NET Core application can be built to test the flow.
Recently, I have had to specify the configuration of a RabbitMQ server and integrate a .NET application with it. To do so, I had some concerns, such as:
Backend developer, passionate by .NET, father of a turtle and a chinchilla and step father of three dogs.