In my previous organization, we heavily relied on Tibco messaging solutions like Tibco RD (Rendezvous) and Tibco RV (Rendezvous) for the entire rating system. I have also explored Apache Kafka.

The configuration and setup of Anypoint MQ are easier.

I personally have not explored other queuing solutions, but have used Akka HTTP, with is a fully asynchronous web server of sorts. It's not a queuing system, but I mention it because of the asynchronous behavior. RabbitMQ was perfect for our current solution, however.

We evaluated Apache Kafka, NSQ, and ActiveMQ.

I was considering using ActiveMQ on AWS, but after some research, I decided RabbitMO was a more complex solution and one that is more commonly used, so I chose RabbitMQ over it.

I looked at other service bus/message queue solutions. In particular, I investigated:

• Azure’s Queue Storage: No real service bus ability without plugins
• AWS’s Simple Notification Service: Not much in the way of service bus capability. It did not allow private queues on the fly.
• A few other open-source message brokers

RabbitMQ seemed the most full-featured option for what we needed.

We didn’t have any alternatives. Our company has a contract with PCF, so it was our only option.

We looked at ZeroMQ, Kafka and Redis.

We are also evaluating Apache Kafka. Our process is very disciplined. We look at the analytics, the abstraction, the architecture relative to our technical architecture, we ask ourselves questions about the use case, which is better for use A or B. Kafka is not as simple for “publish and subscribe”. You can do it, but not the best fit for us. However as a queueing system, Kafka is great. The records are stored on the queue in the order they are received, However, you can easily search by topic no matter how large the list. Important if you keep track of everything.

We looked at MSMQ, NServiceBus, Azure Service Bus, and Apache Kafka.

Yes, I evaluated Kafka.

Kafka is more suitable to large amount events in order. RabbitMQ is more suitable to the related small amount of messages, which is my situation and I don’t care about the message order.

We evaluated several other solutions; the MQSeries and MSMQ.

We looked at Kafka, but we needed the routing as well.

We also evaluated ZeroMQ and EasyNetQ.

I am not aware of other evaluated options.

I have looked at Apache ActiveMQ and Kafka.

I did not look into other solutions.

We chose this solution around 2010, so there weren’t many options at the time. We evaluated the native JMS method and it didn't scale up well.

We researched ZeroMQ, RabbitMQ, and Kafka. We found that Kafka was a bit of an overkill because our requirements were quite simple. RabbitMQ was pretty easy to set up, which is why we chose it.

I have evaluated and researched Axon, RabbitMQ, Kafka, and IBM MQ.

We looked at the Redis solution, but it was not a good fit for our needs.

We evaluated Apache Kafka also.

We did not evaluate any other solution prior to this one.