RabbitMQ Previous Solutions

Robert Herrick
Director - Information Technology at a transportation company with 51-200 employees
Our initial solution was a simple web API. We quickly realized that it would be difficult to maintain. Scalability and reliability were my primary concerns. HTTP has no reliable delivery built-in, like AMQP does. Changing API versions would have been more difficult if we had stuck with HTTP. View full review »
SeniorSoabf3
Senior Software Specialist at a security firm with 1,001-5,000 employees
We did not evaluate any previous solutions. View full review »
Mustafa İleri
Principal Software Engineer at a tech company with 501-1,000 employees
We have used different solutions before. We have tried MySQL as a queue and it was terrible. View full review »
Keith Sohl
Senior Developer/Architect at a tech services company with 51-200 employees
No previous solution was used. View full review »
MidLevel24cf
Mid Level Software Engineer at a tech services company with 501-1,000 employees
We had a monolith application. This was our solution to have more of a micro-service architecture View full review »
Van Nguyen
Senior Software Engineer at a hospitality company with 1,001-5,000 employees
We previously used MSMQ. Apparently, it is not as good as RabbitMQ in terms of the features offered. View full review »
AndrewFerguson
Software Engineer with 1,001-5,000 employees
To my knowledge, this is the only queuing system my company has used. View full review »
Developmeb7c
Development Lead - Java/Hybris with 10,001+ employees
We analyzed our requirement thoroughly and were sure that RabbitMQ was the solution for us. We didn’t look at anything else. View full review »
Boris Levin
Head of Data & Infrastructure at a tech services company with 51-200 employees
We tested some earlier version of Apache Kafka, but it wasn't stable enough at the time. At the moment, we're considering switching back to Apache Kafka. View full review »
VpOfSoftb75e
VP of Software at a manufacturing company with 11-50 employees
We evaluated a variety of message products and found that for the feature set RabbitMQ was the best. View full review »
Solution44bd
Solutions Architect at a tech services company with 1,001-5,000 employees
Initially, we were using the BizTalk and Redis solutions. The reason why we switched over was because we were looking for better support in Celery task management and other programming languages. We were looking for a much more stable and secure solution. View full review »
Softwareace4
Software Engineer at a marketing services firm with 51-200 employees
We have used DBus and ZeroMQ. We wanted something more reliable and simple, so we switched over to this tool. View full review »
Andrew-Ferguson
Software Engineer at a tech vendor with 1,001-5,000 employees
We did not have a previous solution. View full review »
Todd Outten
Founder Partner and CTO at Rogue Startup
We were using IBM MQ, but it was too costly and not open source. View full review »
Nikola Tzaprev
Head of Cloud Platform Development at a tech vendor with 501-1,000 employees
This is the first solution we implemented. View full review »
Presidenf9d6
President, Applications and Security Architect at a tech services company with 51-200 employees
I am not aware of any previous solutions. View full review »
Shashidhar Kondra
Technical Manager with 501-1,000 employees
Initially, we were using different queuing technologies. Due to the message routing feature and flexibility that RabbitMQ provided, we made the switch to this tool. View full review »
Ray Collins
IT Manager at a financial services firm with 1,001-5,000 employees
I have used IBM MQ software, but it was not applicable to this application. View full review »

Sign Up with Email