CoolAMQP
Support for Python 3 is suspended until I fix pending issues
When you're tired of fucking with AMQP reconnects.
When a connection made by CoolAMQP to your broker fails, it will pick another node, redeclare exchanges, queues, consumers, QoS and all the other shit, and tell your application that a disconnect happened.
You only need to remember that:
- Reconnects and redefinitions take a while.
- Things will happen during that time. It is your responsibility to ensure that your distributed system is built to handle this
- CoolAMQP will tell you when it senses losing broker connection.
- It will also tell you when it regains the connection (that means that everything is redefined and ready to go)
- Delivering messages multiple times may happen.
- Ensure you know when it happens. Keywords: message acknowledgement, amqp specification
The project is actively maintained, used in a commercial project and unit tested with high coverage.
Enjoy!
todo
- Allow binding queues with exchanges with a routing_key