✳flâneur — a map of the web's best reading

RabbitMQ tutorial - Reliable Publishing with Publisher Confirms — RabbitMQ

rabbitmq.com · 1,950 words · saved by 1 readers

This tutorial assumes RabbitMQ is installed and running on localhost on the standard port (5672). In case you use a different host, port or credentials, connections settings would require adjusting. If you're having trouble going through this tutorial you can contact us through the mailing list or RabbitMQ community Slack. Publisher confirms are a RabbitMQ extension to implement reliable publishing. When publisher confirms are enabled on a channel, messages the client publishes are confirmed asynchronously by the broker, meaning they have been taken care of on the server side. In this tutorial we're going to use publisher confirms to make sure published messages have safely reached the broker. We will cover several strategies to using publisher confirms and explain their pros and cons. Publisher confirms are a RabbitMQ extension to the AMQP 0.9.1 protocol, so they are not enabled by default. Publisher confirms are enabled at the channel level with the confirmSelect method: This method

On this page Publisher Confirms ​ info Prerequisites ​ This tutorial assumes RabbitMQ is installed and running on localhost on the standard port (5672). In case you use a different host, port or credentials, connections settings would require adjusting. Where to get help ​ If you're having trouble going through this tutorial you can contact us through GitHub Discussions or RabbitMQ community Discord . Publisher confirms are a RabbitMQ extension to implement reliable publishing. When publisher confirms are enabled on a channel, messages the client publishes are confirmed asynchronously by the b

Explore this link on the map →

related reading