Alternatives to Apache RocketMQ logo

Alternatives to Apache RocketMQ

Kafka, RabbitMQ, Amazon SQS, Celery, and ActiveMQ are the most popular alternatives and competitors to Apache RocketMQ.
10
20
+ 1
4

What is Apache RocketMQ and what are its top alternatives?

Apache RocketMQ is a distributed messaging and streaming platform with low latency, high performance and reliability, trillion-level capacity and flexible scalability.
Apache RocketMQ is a tool in the Message Queue category of a tech stack.
Apache RocketMQ is an open source tool with 9.5K GitHub stars and 5K GitHub forks. Here’s a link to Apache RocketMQ's open source repository on GitHub

Apache RocketMQ alternatives & related posts

related Kafka posts

Eric Colson
Eric Colson
Chief Algorithms Officer at Stitch Fix · | 19 upvotes · 290.4K views
atStitch FixStitch Fix
Amazon EC2 Container Service
Amazon EC2 Container Service
Docker
Docker
PyTorch
PyTorch
R
R
Python
Python
Presto
Presto
Apache Spark
Apache Spark
Amazon S3
Amazon S3
PostgreSQL
PostgreSQL
Kafka
Kafka
#AWS
#Etl
#ML
#DataScience
#DataStack
#Data

The algorithms and data infrastructure at Stitch Fix is housed in #AWS. Data acquisition is split between events flowing through Kafka, and periodic snapshots of PostgreSQL DBs. We store data in an Amazon S3 based data warehouse. Apache Spark on Yarn is our tool of choice for data movement and #ETL. Because our storage layer (s3) is decoupled from our processing layer, we are able to scale our compute environment very elastically. We have several semi-permanent, autoscaling Yarn clusters running to serve our data processing needs. While the bulk of our compute infrastructure is dedicated to algorithmic processing, we also implemented Presto for adhoc queries and dashboards.

Beyond data movement and ETL, most #ML centric jobs (e.g. model training and execution) run in a similarly elastic environment as containers running Python and R code on Amazon EC2 Container Service clusters. The execution of batch jobs on top of ECS is managed by Flotilla, a service we built in house and open sourced (see https://github.com/stitchfix/flotilla-os).

At Stitch Fix, algorithmic integrations are pervasive across the business. We have dozens of data products actively integrated systems. That requires serving layer that is robust, agile, flexible, and allows for self-service. Models produced on Flotilla are packaged for deployment in production using Khan, another framework we've developed internally. Khan provides our data scientists the ability to quickly productionize those models they've developed with open source frameworks in Python 3 (e.g. PyTorch, sklearn), by automatically packaging them as Docker containers and deploying to Amazon ECS. This provides our data scientist a one-click method of getting from their algorithms to production. We then integrate those deployments into a service mesh, which allows us to A/B test various implementations in our product.

For more info:

#DataScience #DataStack #Data

See more
John Kodumal
John Kodumal
CTO at LaunchDarkly · | 15 upvotes · 149.9K views
atLaunchDarklyLaunchDarkly
Kafka
Kafka
Amazon Kinesis
Amazon Kinesis
Redis
Redis
Amazon EC2
Amazon EC2
Amazon ElastiCache
Amazon ElastiCache
Consul
Consul
Patroni
Patroni
TimescaleDB
TimescaleDB
PostgreSQL
PostgreSQL
Amazon RDS
Amazon RDS

As we've evolved or added additional infrastructure to our stack, we've biased towards managed services. Most new backing stores are Amazon RDS instances now. We do use self-managed PostgreSQL with TimescaleDB for time-series data—this is made HA with the use of Patroni and Consul.

We also use managed Amazon ElastiCache instances instead of spinning up Amazon EC2 instances to run Redis workloads, as well as shifting to Amazon Kinesis instead of Kafka.

See more

related RabbitMQ posts

James Cunningham
James Cunningham
Operations Engineer at Sentry · | 18 upvotes · 119.2K views
atSentrySentry
RabbitMQ
RabbitMQ
Celery
Celery
#MessageQueue

As Sentry runs throughout the day, there are about 50 different offline tasks that we execute—anything from “process this event, pretty please” to “send all of these cool people some emails.” There are some that we execute once a day and some that execute thousands per second.

Managing this variety requires a reliably high-throughput message-passing technology. We use Celery's RabbitMQ implementation, and we stumbled upon a great feature called Federation that allows us to partition our task queue across any number of RabbitMQ servers and gives us the confidence that, if any single server gets backlogged, others will pitch in and distribute some of the backlogged tasks to their consumers.

#MessageQueue

See more
Tim Abbott
Tim Abbott
Founder at Zulip · | 10 upvotes · 69.8K views
atZulipZulip
Redis
Redis
Python
Python
RabbitMQ
RabbitMQ

We've been using RabbitMQ as Zulip's queuing system since we needed a queuing system. What I like about it is that it scales really well and has good libraries for a wide range of platforms, including our own Python. So aside from getting it running, we've had to put basically 0 effort into making it scale for our needs.

However, there's several things that could be better about it: * It's error messages are absolutely terrible; if ever one of our users ends up getting an error with RabbitMQ (even for simple things like a misconfigured hostname), they always end up needing to get help from the Zulip team, because the errors logs are just inscrutable. As an open source project, we've handled this issue by really carefully scripting the installation to be a failure-proof configuration (in this case, setting the RabbitMQ hostname to 127.0.0.1, so that no user-controlled configuration can break it). But it was a real pain to get there and the process of determining we needed to do that caused a significant amount of pain to folks installing Zulip. * The pika library for Python takes a lot of time to startup a RabbitMQ connection; this means that Zulip server restarts are more disruptive than would be ideal. * It's annoying that you need to run the rabbitmqctl management commands as root.

But overall, I like that it has clean, clear semanstics and high scalability, and haven't been tempted to do the work to migrate to something like Redis (which has its own downsides).

See more

related Amazon SQS posts

Tim Specht
Tim Specht
‎Co-Founder and CTO at Dubsmash · | 14 upvotes · 68.1K views
atDubsmashDubsmash
Google BigQuery
Google BigQuery
Amazon SQS
Amazon SQS
AWS Lambda
AWS Lambda
Amazon Kinesis
Amazon Kinesis
Google Analytics
Google Analytics
#ServerlessTaskProcessing
#GeneralAnalytics
#RealTimeDataProcessing
#BigDataAsAService

In order to accurately measure & track user behaviour on our platform we moved over quickly from the initial solution using Google Analytics to a custom-built one due to resource & pricing concerns we had.

While this does sound complicated, it’s as easy as clients sending JSON blobs of events to Amazon Kinesis from where we use AWS Lambda & Amazon SQS to batch and process incoming events and then ingest them into Google BigQuery. Once events are stored in BigQuery (which usually only takes a second from the time the client sends the data until it’s available), we can use almost-standard-SQL to simply query for data while Google makes sure that, even with terabytes of data being scanned, query times stay in the range of seconds rather than hours. Before ingesting their data into the pipeline, our mobile clients are aggregating events internally and, once a certain threshold is reached or the app is going to the background, sending the events as a JSON blob into the stream.

In the past we had workers running that continuously read from the stream and would validate and post-process the data and then enqueue them for other workers to write them to BigQuery. We went ahead and implemented the Lambda-based approach in such a way that Lambda functions would automatically be triggered for incoming records, pre-aggregate events, and write them back to SQS, from which we then read them, and persist the events to BigQuery. While this approach had a couple of bumps on the road, like re-triggering functions asynchronously to keep up with the stream and proper batch sizes, we finally managed to get it running in a reliable way and are very happy with this solution today.

#ServerlessTaskProcessing #GeneralAnalytics #RealTimeDataProcessing #BigDataAsAService

See more
Praveen Mooli
Praveen Mooli
Technical Leader at Taylor and Francis · | 11 upvotes · 174.7K views
MongoDB Atlas
MongoDB Atlas
Amazon S3
Amazon S3
Amazon DynamoDB
Amazon DynamoDB
Amazon RDS
Amazon RDS
Serverless
Serverless
Docker
Docker
Terraform
Terraform
Travis CI
Travis CI
GitHub
GitHub
RxJS
RxJS
Angular 2
Angular 2
AWS Lambda
AWS Lambda
Amazon SQS
Amazon SQS
Amazon SNS
Amazon SNS
Amazon Kinesis Firehose
Amazon Kinesis Firehose
Amazon Kinesis
Amazon Kinesis
Flask
Flask
Python
Python
ExpressJS
ExpressJS
Node.js
Node.js
Spring Boot
Spring Boot
Java
Java
#Backend
#Microservices
#Eventsourcingframework
#Webapps
#Devops
#Data

We are in the process of building a modern content platform to deliver our content through various channels. We decided to go with Microservices architecture as we wanted scale. Microservice architecture style is an approach to developing an application as a suite of small independently deployable services built around specific business capabilities. You can gain modularity, extensive parallelism and cost-effective scaling by deploying services across many distributed servers. Microservices modularity facilitates independent updates/deployments, and helps to avoid single point of failure, which can help prevent large-scale outages. We also decided to use Event Driven Architecture pattern which is a popular distributed asynchronous architecture pattern used to produce highly scalable applications. The event-driven architecture is made up of highly decoupled, single-purpose event processing components that asynchronously receive and process events.

To build our #Backend capabilities we decided to use the following: 1. #Microservices - Java with Spring Boot , Node.js with ExpressJS and Python with Flask 2. #Eventsourcingframework - Amazon Kinesis , Amazon Kinesis Firehose , Amazon SNS , Amazon SQS, AWS Lambda 3. #Data - Amazon RDS , Amazon DynamoDB , Amazon S3 , MongoDB Atlas

To build #Webapps we decided to use Angular 2 with RxJS

#Devops - GitHub , Travis CI , Terraform , Docker , Serverless

See more

related Celery posts

James Cunningham
James Cunningham
Operations Engineer at Sentry · | 18 upvotes · 119.2K views
atSentrySentry
RabbitMQ
RabbitMQ
Celery
Celery
#MessageQueue

As Sentry runs throughout the day, there are about 50 different offline tasks that we execute—anything from “process this event, pretty please” to “send all of these cool people some emails.” There are some that we execute once a day and some that execute thousands per second.

Managing this variety requires a reliably high-throughput message-passing technology. We use Celery's RabbitMQ implementation, and we stumbled upon a great feature called Federation that allows us to partition our task queue across any number of RabbitMQ servers and gives us the confidence that, if any single server gets backlogged, others will pitch in and distribute some of the backlogged tasks to their consumers.

#MessageQueue

See more
Michael Mota
Michael Mota
CEO & Founder at AlterEstate · | 4 upvotes · 15K views
atAlterEstateAlterEstate
Django
Django
RabbitMQ
RabbitMQ
Celery
Celery

Automations are what makes a CRM powerful. With Celery and RabbitMQ we've been able to make powerful automations that truly works for our clients. Such as for example, automatic daily reports, reminders for their activities, important notifications regarding their client activities and actions on the website and more.

We use Celery basically for everything that needs to be scheduled for the future, and using RabbitMQ as our Queue-broker is amazing since it fully integrates with Django and Celery storing on our database results of the tasks done so we can see if anything fails immediately.

See more

related ActiveMQ posts

Naushad Warsi
Naushad Warsi
software developer at klingelnberg · | 1 upvotes · 51.3K views
RabbitMQ
RabbitMQ
ActiveMQ
ActiveMQ

I use ActiveMQ because RabbitMQ have stopped giving the support for AMQP 1.0 or above version and the earlier version of AMQP doesn't give the functionality to support OAuth.

If OAuth is not required and we can go with AMQP 0.9 then i still recommend rabbitMq.

See more
ZeroMQ logo

ZeroMQ

144
130
49
144
130
+ 1
49
Fast, lightweight messaging library that allows you to design complex communication system without much effort
ZeroMQ logo
ZeroMQ
VS
Apache RocketMQ logo
Apache RocketMQ
MQTT logo

MQTT

81
41
0
81
41
+ 1
0
A machine-to-machine Internet of Things connectivity protocol
    Be the first to leave a pro
    MQTT logo
    MQTT
    VS
    Apache RocketMQ logo
    Apache RocketMQ
    WCF logo

    WCF

    42
    16
    0
    42
    16
    + 1
    0
    A runtime and a set of APIs for building connected, service-oriented applications
      Be the first to leave a pro
      WCF logo
      WCF
      VS
      Apache RocketMQ logo
      Apache RocketMQ
      Kafka Manager logo

      Kafka Manager

      39
      46
      0
      39
      46
      + 1
      0
      A tool for managing Apache Kafka, developed by Yahoo
        Be the first to leave a pro
        Kafka Manager logo
        Kafka Manager
        VS
        Apache RocketMQ logo
        Apache RocketMQ

        related Kafka Manager posts

        Conor Myhrvold
        Conor Myhrvold
        Tech Brand Mgr, Office of CTO at Uber · | 5 upvotes · 133.1K views
        atUber TechnologiesUber Technologies
        Kafka Manager
        Kafka Manager
        Kafka
        Kafka
        GitHub
        GitHub
        Apache Spark
        Apache Spark
        Hadoop
        Hadoop

        Why we built Marmaray, an open source generic data ingestion and dispersal framework and library for Apache Hadoop :

        Built and designed by our Hadoop Platform team, Marmaray is a plug-in-based framework built on top of the Hadoop ecosystem. Users can add support to ingest data from any source and disperse to any sink leveraging the use of Apache Spark . The name, Marmaray, comes from a tunnel in Turkey connecting Europe and Asia. Similarly, we envisioned Marmaray within Uber as a pipeline connecting data from any source to any sink depending on customer preference:

        https://eng.uber.com/marmaray-hadoop-ingestion-open-source/

        (Direct GitHub repo: https://github.com/uber/marmaray Kafka Kafka Manager )

        See more
        Azure Service Bus logo

        Azure Service Bus

        37
        8
        0
        37
        8
        + 1
        0
        Reliable cloud messaging as a service (MaaS)
          Be the first to leave a pro
          Azure Service Bus logo
          Azure Service Bus
          VS
          Apache RocketMQ logo
          Apache RocketMQ
          Mosquitto logo

          Mosquitto

          28
          20
          2
          28
          20
          + 1
          2
          An open source message broker that implements the MQTT protocol
          Mosquitto logo
          Mosquitto
          VS
          Apache RocketMQ logo
          Apache RocketMQ
          Confluent logo

          Confluent

          24
          10
          5
          24
          10
          + 1
          5
          A stream data platform to help companies harness their high volume real-time data streams
          Confluent logo
          Confluent
          VS
          Apache RocketMQ logo
          Apache RocketMQ
          XMPP logo

          XMPP

          19
          11
          0
          19
          11
          + 1
          0
          An open XML technology for real-time communication
            Be the first to leave a pro
            XMPP logo
            XMPP
            VS
            Apache RocketMQ logo
            Apache RocketMQ
            NServiceBus logo

            NServiceBus

            19
            6
            0
            19
            6
            + 1
            0
            Enterprise-grade scalability and reliability for your workflows and integrations
              Be the first to leave a pro
              NServiceBus logo
              NServiceBus
              VS
              Apache RocketMQ logo
              Apache RocketMQ
              IBM MQ logo

              IBM MQ

              18
              21
              0
              18
              21
              + 1
              0
              Enterprise-grade messaging middleware
                Be the first to leave a pro
                IBM MQ logo
                IBM MQ
                VS
                Apache RocketMQ logo
                Apache RocketMQ