Introduction
Configuration
Language Support
AMQP 0-9-1 Overview
- The AMQP Protocol
- Connections & Channels
- Queues
- Messages
- Bindings
- Exchanges
- Vhost
- Publishers and Consumers
More Exchange Types
More Consumer Features
Queue Deep-dive
Other Features
Reliable Message Delivery
High Availability and Backup
Monitoring
Management HTTP API
Tutorials
Networking
LavinMQ CLI
Overview
In LavinMQ, reliable message delivery is vital to prevent message loss in specific scenarios like server failures, network interruptions, or high message traffic.
To ensure data safety, LavinMQ offers various mechanisms for reliable message delivery. You can achieve this by employing one or a combination of the following methods:
- Publisher Confirms
- Consumer Acknowledgements
- Durable Queues and Persistent Messages
- Transactions
Publisher Confirms
When using publisher confirms, the producer (publisher) receives acknowledgments from LavinMQ after successfully delivering messages to the intended queues. This feedback mechanism assures the producer that messages have been reliably accepted by LavinMQ.
For more information, you can read our documentation on publisher confirms.
Consumer Acknowledgements
On the other hand, when consumers consume messages from a queue, they can also send an acknowledgement to LavinMQ confirming the successful processing of messages. If an acknowledgment isn’t received, LavinMQ assumes something went wrong and the message is left in the queue.
For more information, you can read our documentation on consumer acknowledgements.
Durable Queues and Persistent Messages
Declaring queues as “durable” ensures that they survive server restarts, safeguarding your messages from loss.
In LavinMQ, messages are persistent by default. LavinMQ would generally ignore the
delivery_mode argument, if passed.
Transactions
Even though publisher confirms and consumer acknowledgements offer some level of message persistence guarantee in LavinMQ, that guarante is not 100%.
Transactions in LavinMQ offer the highest level of message persistence guarantee.
To learn more about transactions in LavinMQ and how they offer the highest level of message durability guarantee compared to pubisher confirms and consumer acknowledgements, check out our documentation on transactions.
Wrap up
By leveraging these methods in LavinMQ, you can establish a robust and reliable message delivery system, preventing data loss and ensuring your messaging infrastructure performs optimally even in challenging circumstances.
Ready to take the next steps? Here are some things you should keep in mind:
Managed LavinMQ instance on CloudAMQP
LavinMQ has been built with performance and ease of use in mind - we've benchmarked a throughput of about 1,000,000 messages/sec. You can try LavinMQ without any installation hassle by creating a free instance on CloudAMQP. Signing up is a breeze.
Help and feedback
We welcome your feedback and are eager to address any questions you may have about this piece or using LavinMQ. Join our Slack channel to connect with us directly. You can also find LavinMQ on GitHub.