Overview

RabbitMQ

Stacks21.7K

Followers18.9K

Votes558

GitHub Stars13.2K

Forks4.0K

Heroku Redis

Stacks105

Followers163

Votes5

Heroku Redis vs RabbitMQ: What are the differences?

Introduction

In this comparison, we will outline the key differences between Heroku Redis and RabbitMQ, two popular tools used in managing data and communication within applications.

Data Structure: Heroku Redis is a key-value store used for caching, while RabbitMQ is a message broker for handling asynchronous communication between microservices or components. Redis is optimal for quick data retrieval; RabbitMQ allows for decoupling of components and ensuring message delivery.
Use Case: Heroku Redis is ideal for storing small pieces of data that need to be accessed frequently for improving application performance, such as session data or configuration settings. In contrast, RabbitMQ is suited for handling complex communication patterns among various services, enabling loose coupling and scalability.
Persistence: Heroku Redis supports data persistence by periodically writing to disk, allowing data to be recovered even after a restart. RabbitMQ, on the other hand, does not inherently offer persistence, but it can be configured to save messages to disk for fault tolerance.
Message Queuing: RabbitMQ specializes in message queuing, enabling message delivery between applications by using different exchange types like direct, topic, or fanout. Heroku Redis does not have built-in message queuing capabilities but focuses on data caching for enhancing performance.
Scaling: Heroku Redis can easily scale by adding read replicas to handle increased read traffic, distributing the load efficiently. RabbitMQ can be scaled by setting up a cluster of nodes to handle high message throughput while maintaining reliability and fault tolerance.
Monitoring and Management: Heroku Redis provides monitoring tools like metrics, alerts, and log access for tracking performance and troubleshooting issues. RabbitMQ offers management features to oversee exchanges, queues, and connections, ensuring smooth operation and detecting potential bottlenecks.

In Summary, the key differences between Heroku Redis and RabbitMQ lie in their data structure, use cases, persistence mechanisms, messaging capabilities, scalability options, and monitoring tools.

🔥 Trending in Background Jobs on StackShare

Solid Queue Background Jobs

Database-backed active job backend

Try it View Docs Alternatives

Try

0

1

Advice on RabbitMQ, Heroku Redis

viradiya

Apr 12, 2020

Needs adviceon

AngularJS

ASP.NET Core

MSSQL

We are going to develop a microservices-based application. It consists of AngularJS, ASP.NET Core, and MSSQL.

We have 3 types of microservices. Emailservice, Filemanagementservice, Filevalidationservice

I am a beginner in microservices. But I have read about RabbitMQ, but come to know that there are Redis and Kafka also in the market. So, I want to know which is best.

933k views933k

Comments

Meili

Software engineer at Digital Science

Sep 24, 2020

Needs adviceon

ZeroMQ

RabbitMQ

Amazon SQS

Hi, we are in a ZMQ set up in a push/pull pattern, and we currently start to have more traffic and cases that the service is unavailable or stuck. We want to:

Not loose messages in services outages
Safely restart service without losing messages (@{ZeroMQ}|tool:1064| seems to need to close the socket in the receiver before restart manually)

Do you have experience with this setup with ZeroMQ? Would you suggest RabbitMQ or Amazon SQS (we are in AWS setup) instead? Something else?

Thank you for your time

500k views500k

Comments

André

Technology Manager at GS1 Portugal - Codipor

Jul 30, 2020

Needs adviceon

.NET Core

Hello dear developers, our company is starting a new project for a new Web App, and we are currently designing the Architecture (we will be using .NET Core). We want to embark on something new, so we are thinking about migrating from a monolithic perspective to a microservices perspective. We wish to containerize those microservices and make them independent from each other. Is it the best way for microservices to communicate with each other via ESB, or is there a new way of doing this? Maybe complementing with an API Gateway? Can you recommend something else different than the two tools I provided?

We want something good for Cost/Benefit; performance should be high too (but not the primary constraint).

Thank you very much in advance :)

461k views461k

Comments

Detailed Comparison

RabbitMQ	Heroku Redis
RabbitMQ gives your applications a common platform to send and receive messages, and your messages a safe place to live until received.	Heroku Redis is an in-memory key-value data store, run by Heroku, that is provisioned and managed as an add-on. Heroku Redis is accessible from any language with a Redis driver, including all languages and frameworks supported by Heroku.
Robust messaging for applications;Easy to use;Runs on all major operating systems;Supports a huge number of developer platforms;Open source and commercially supported	Easily Optimize;Vertically Scalable
Statistics
GitHub Stars 13.2K	GitHub Stars -
GitHub Forks 4.0K	GitHub Forks -
Stacks 21.7K	Stacks 105
Followers 18.9K	Followers 163
Votes 558	Votes 5
Pros & Cons
Pros 235 It's fast and it works with good metrics/monitoring 80 Ease of configuration 60 I like the admin interface 52 Easy to set-up and start with 22 Durable Cons 9 Too complicated cluster/HA config and management 6 Needs Erlang runtime. Need ops good with Erlang runtime 5 Configuration must be done first, not by your code 4 Slow	Pros 5 More reliable than the other Redis add-ons Cons 1 More expensive than the other options
Integrations
No integrations available	Heroku Redis

What are some alternatives to RabbitMQ, Heroku Redis?

Kafka

Kafka is a distributed, partitioned, replicated commit log service. It provides the functionality of a messaging system, but with a unique design.

Celery

Celery is an asynchronous task queue/job queue based on distributed message passing. It is focused on real-time operation, but supports scheduling as well.

Amazon SQS

Transmit any volume of data, at any level of throughput, without losing messages or requiring other services to be always available. With SQS, you can offload the administrative burden of operating and scaling a highly available messaging cluster, while paying a low price for only what you use.

NSQ

NSQ is a realtime distributed messaging platform designed to operate at scale, handling billions of messages per day. It promotes distributed and decentralized topologies without single points of failure, enabling fault tolerance and high availability coupled with a reliable message delivery guarantee. See features & guarantees.

ActiveMQ

Apache ActiveMQ is fast, supports many Cross Language Clients and Protocols, comes with easy to use Enterprise Integration Patterns and many advanced features while fully supporting JMS 1.1 and J2EE 1.4. Apache ActiveMQ is released under the Apache 2.0 License.

ZeroMQ

The 0MQ lightweight messaging kernel is a library which extends the standard socket interfaces with features traditionally provided by specialised messaging middleware products. 0MQ sockets provide an abstraction of asynchronous message queues, multiple messaging patterns, message filtering (subscriptions), seamless access to multiple transport protocols and more.

Apache NiFi

An easy to use, powerful, and reliable system to process and distribute data. It supports powerful and scalable directed graphs of data routing, transformation, and system mediation logic.

Gearman

Gearman allows you to do work in parallel, to load balance processing, and to call functions between languages. It can be used in a variety of applications, from high-availability web sites to the transport of database replication events.

Memphis

Highly scalable and effortless data streaming platform. Made to enable developers and data teams to collaborate and build real-time and streaming apps fast.

IronMQ

An easy-to-use highly available message queuing service. Built for distributed cloud applications with critical messaging needs. Provides on-demand message queuing with advanced features and cloud-optimized performance.