RabbitMQ vs. Amazon SQS vs. ActiveMQ

Implements the TaskQueue API.

The 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.

MQ

RabbitMQ 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.

celery broker 로써 erlang 기반의 rabbitmq 를 클러스터링 구성하여 적용 하였습니다.

Rabbit 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.

RabbitMQ is used by Celery as a task queue.

Services inner communication and logging

Work queue and delayed messages are still managed in RabbitMQ, phasing out

RabbitMQ is the enterprise message bus for our platform, providing infrastructure for managing our ETL queues, real-time event notifications for applications, and audit logging.

Our primary message queuing system.

RabbitMQ 学习总结

To support event-driven architecture.

All communication between our services is asynchronous and goes through a message queue.

AMQP 0-9-1 with topic exchanges for fast & reliable messaging. Built on the rock-solid Erlang OTP.

We used RabbitMQ in conjunction with Celery (Celery-Beat package) to run periodic tasks on the server.

Communication between microservices.

Message bus for application messages (commands, events) and logs. Creates transparency into pending units of work. Stored pending work in case of application failures.

default message queue replacing generic crons

We use RabbitMQ quite heavily across both legacy and current products for everything from work queues to communications products and messaging.

All changes to our resources are published to RabbitMQ, and is the core of our evented architecture.

Queue for agents to pick up jobs from, and provide logs back to front-end UI consumers and the log server.

Decoupling various backend services

Messaging Bus

Used 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.

wonderful messaging service. used it at a couple companies.

Experience with RabbitMQ in the context of handling asynchronous api events + inter-server communication.

Used at cloudfind as one of the job queue technologies.

Task queue

Use like a service bus for microservices

IoT communication, topic based message system

消息队列

Set-and-forget backend for NServicebus. Easy to deploy and develop for.

Data pipeline

We attentively enroll in classes and seminars to keep on our education. Every year we attain far more hours of knowledge than required to sustain our licenses.

Asynchronous communication from Backend to Worker processes

Reliable inter-service messaging with failover and error routing. Used heavily in backend infrastructure for long-lived tasks.

Primary message queue. Enqueueing operations revert to a local file-system-based queue when SQS is unavailable.

In the beginning we thought we wanted to start using something like RabbitMQ or maybe Kafka or maybe ActiveMQ. Back then we only had a few developers and no ops people. That has changed now, but we didn't really look forward to setting up a queuing cluster and making sure that all works.

What we did instead was we looked at what services Amazon offers to see if we can use those to build our own messaging system within those services. That's basically what we did. We wrote some clients in Ruby that can basically do the entire orchestration for us, and we run all our messaging on both SNS and SQS. Basically what you can do in Amazon services is you can use Amazon Simple Notification Service, so SNS, for creating topics and you can use queues to subscribe to these topics. That's basically all you need for a messaging system. You don't have to worry about scalability at all. That's what really appealed to us.

Message queue for our Elastic Beanstalk worker environments.

SQS is the bridge between our new Lambda services and our incumbent Rails applications. Extremely easy to use when you're already using other AWS infrastructure.

https://ifunny.co

Great pick-n-go queue, be prepared for occasionally outage in especially us-east-1 region.

Distributed background job queue.

I can't afford to lose data if Dynamo throttles my writes, so everything goes into a message queue first.

This isn't exactly low-latency (10s to 100s of milliseconds), but it has good throughput and a simple API. There is good reliability, and there is no configuration necessary to get up and running. A hosted queue is important when trying to move fast.

비디오 프로세싱 요청 메시지 큐
컨텐츠 배포 요청 메시지 큐

Message queue that the Raspberry Pi will retrieve messages.

For asynchronous data processing

Batch processing.

Remote broker and local client for incoming data feeds. Local broker for republishing data feeds to other systems.