RabbitMQ no longer loses message with the use of Alternate Exchange and fanout

Posting a message in RabbitMQ is very easy, unfortunately RabbitMQ does not provide any feedback on the success or failure of the delivery in a queue. A simple typo in the routing key and the message will be lost forever without being informed. The Alternate Exchange option allows you to retrieves these "lost" messages in a specific queue. Read the post

Control the number of retries of a message with x-death header in RabbitMQ

Sometimes the processing of a message causes an error. In this case, it is common to move this message to another queue to try to process it later. All this, can be automated in RabbitMQ with the DLX / DLK option and the application of a TTL. But be careful not to create an infinite loop of attempted treatment, in this article I will introduce x-death header to control the number of retries. Read the post

Use Dead Letter in RabbitMQ to delay messages in case of error

RabbitMQ is fast, sometimes a bit too much compared to the rest of the infrastructure. A database replication delay can crash the processing of a message. I show you how I handle this problem and use the dead letter exchange and dead letter routing key options to delay the processing of a message. Read the post