Overall Satisfaction with Pivotal RabbitMQ
We used Pivotal RabbitMQ in order to develop our own framework. We have a custom architecture to distribute task and commands between our micro services. The effect of RabbitMQ reached all organization as we developed Administration backend UIs for all departments.
The organization managed users and the project using RabbitMQ.
Previously, in other organization we used it as medium to communicate nano-services following a similar pattern as previously described.
- Document the internal processes of Pivotal RabbitMQ so you fully understand what can and cannot do.
- Concurrency and resource utilization.
- Handling dead letter queues and giving flexibility to create your own dead letter systems.
- AMQL 0.9.1 is extremely flexible.
- Shovels are quite raw to use.
- More AMQP extensions like the publisher confirmation for not requiring so many queues.
- Easy AMQP entities configuration changes on production.
- Solace PubSub+
It is just better documented and seems a better fit given that is done using erlang. PubSub+ low level approach seems unsafe. They work with custom hardware whereas Pivotal RabbitMQ seem a better fit for generic hardware (cloud).
Do you think RabbitMQ delivers good value for the price?
Are you happy with RabbitMQ's feature set?
Did RabbitMQ live up to sales and marketing promises?
I wasn't involved with the selection/purchase process
Did implementation of RabbitMQ go as expected?
Would you buy RabbitMQ again?