Overall Satisfaction with RabbitMQ
We currently use RabbitMQ to manage a majority of our outgoing emails, text messages, and faxes from a variety of different systems across the entire business. RabbitMQ sends outgoing notifications by brokering messages from producer (the source system) to consumer (the destination endpoint). For faxing our MQ instance takes in a message, generates a binary PDF file and drops it on an ActiveFax server (running on Windows 2012). For email notifications, we integrate of office 365 and for SMS we use a cloud-base provider. We a system to manage and store outgoing templates which are used during the message brokering process to send the correct notification template
- High Performance
- Integrates well with Spring
- Easy Setup
- Not a lot of tooling
- Hard to get into the internals
- Not incorporated in many enterprise systems
- Solved outgoing communication issues
- Solved performance issues with traditional request/response services
- Solved batch image processing issues (in conjunction with other solutions)
None of the options in the list are really similar products. We use Apache Camel in conjunction with RabbitMQ and we also use Oracle Integration Cloud and WSO2 for messaging. Integration Cloud is SaaS-based and low code, so it's drastically different in that regard. WS02 is more similar in that it is much less abstracted but supports a wider range of message types.