What is Kafka?
What is NSQ?
What is RabbitMQ?
Want advice about which of these to choose?Ask the StackShare community!
Why do developers choose Kafka?
Why do developers choose NSQ?
Why do developers choose RabbitMQ?
- Durable16
Sign up to add, upvote and see more prosMake informed product decisions
What are the cons of using Kafka?
What are the cons of using NSQ?
- HA1
What are the cons of using RabbitMQ?
- Slow2
What companies use Kafka?
What companies use NSQ?
Sign up to get full access to all the companiesMake informed product decisions
What tools integrate with Kafka?
What tools integrate with NSQ?
What tools integrate with RabbitMQ?
Sign up to get full access to all the tool integrationsMake informed product decisions
RabbitMQI developed one of the largest queue based medical results delivery systems in the world, 18,000+ queues and still growing over a decade later all using MQSeries, later called Websphere MQ. When I left that company I started using RabbitMQ after doing some research on free offerings.. it works brilliantly and is incredibly flexible from small scale single instance use to large scale multi-server - multi-site architectures.
If you can think in queues then RabbitMQ should be a viable solution for integrating disparate systems.
Kafka
Front-end messages are logged to Kafka by our API and application servers. We have batch processing (on the middle-left) and real-time processing (on the middle-right) pipelines to process the experiment data. For batch processing, after daily raw log get to s3, we start our nightly experiment workflow to figure out experiment users groups and experiment metrics. We use our in-house workflow management system Pinball to manage the dependencies of all these MapReduce jobs.
RabbitMQThe poster child for scalable messaging systems, RabbitMQ has been used in countless large scale systems as the messaging backbone of any large cluster, and has proven itself time and again in many production settings.
RabbitMQRabbit acts as our coordinator for all actions that happen during game time. All worker containers connect to rabbit in order to receive game events and emit their own events when applicable.
RabbitMQUsed as central Message Broker; off-loading tasks to be executed asynchronous, used as communication tool between different microservices, used as tool to handle peaks in incoming data, etc.
RabbitMQRabbitMQ is the enterprise message bus for our platform, providing infrastructure for managing our ETL queues, real-time event notifications for applications, and audit logging.
RabbitMQRabbitMQ is an all purpose queuing service for our stack. We use it for user facing jobs as well as keeping track of behind the scenes jobs.
KafkaBuilding out real-time streaming server to present data insights to Coolfront Mobile customers and internal sales and marketing teams.
NSQThe built-in Gamification that comes with our Playbooks application uses NSQ for work queues and microservice communication.
KafkaWe are using Kafka as a message queue to process our widget logs.
KafkaUsed for communications and triggering jobs across ETL systems
KafkaUsed as a integration middleware by messaging interchanging.