IronWorker vs RabbitMQ

Overview

RabbitMQ

Stacks21.8K

Followers18.9K

Votes558

GitHub Stars13.2K

Forks4.0K

IronWorker

Stacks39

Followers17

Votes0

IronWorker vs RabbitMQ: What are the differences?

IronWorker: High-Scale Async Task Processing. IronWorker provides the muscle for modern applications by efficiently isolating the code and dependencies of individual tasks to be processed on demand. Run in a multi-language containerized environment with streamlined orchestration, IronWorker gives you the flexibility to power any task in parallel at massive scale; RabbitMQ: A messaging broker - an intermediary for messaging. RabbitMQ gives your applications a common platform to send and receive messages, and your messages a safe place to live until received.

IronWorker can be classified as a tool in the "Serverless / Task Processing" category, while RabbitMQ is grouped under "Message Queue".

Some of the features offered by IronWorker are:

Containerized Environment
High-Scale Processing
Flexible Scheduling

On the other hand, RabbitMQ provides the following key features:

Robust messaging for applications
Easy to use
Runs on all major operating systems

RabbitMQ is an open source tool with 5.95K GitHub stars and 1.78K GitHub forks. Here's a link to RabbitMQ's open source repository on GitHub.

Share your Stack

Help developers discover the tools you use. Get visibility for your team's tech choices and contribute to the community's knowledge.

View Docs

CLI (Node.js)

Manual

Advice on RabbitMQ, IronWorker

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	IronWorker
RabbitMQ gives your applications a common platform to send and receive messages, and your messages a safe place to live until received.	IronWorker provides the muscle for modern applications by efficiently isolating the code and dependencies of individual tasks to be processed on demand. Run in a multi-language containerized environment with streamlined orchestration, IronWorker gives you the flexibility to power any task in parallel at massive scale.
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	Containerized environment;High-scale processing;Flexible scheduling;Reliable and secure;Detailed monitoring and configuration;Multiple language support
Statistics
GitHub Stars 13.2K	GitHub Stars -
GitHub Forks 4.0K	GitHub Forks -
Stacks 21.8K	Stacks 39
Followers 18.9K	Followers 17
Votes 558	Votes 0
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 0 Can run Docker containers 0 Language agnostic 0 Cloud agnostic 0 Fully on-premise deployable 0 Great customer support

What are some alternatives to RabbitMQ, IronWorker?

Kafka

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

AWS Lambda

AWS Lambda is a compute service that runs your code in response to events and automatically manages the underlying compute resources for you. You can use AWS Lambda to extend other AWS services with custom logic, or create your own back-end services that operate at AWS scale, performance, and security.

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.

Azure Functions

Azure Functions is an event driven, compute-on-demand experience that extends the existing Azure application platform with capabilities to implement code triggered by events occurring in virtually any Azure or 3rd party service as well as on-premises systems.

Google Cloud Run

A managed compute platform that enables you to run stateless containers that are invocable via HTTP requests. It's serverless by abstracting away all infrastructure management.

Related Comparisons

Some of the features offered by IronWorker are:

Containerized Environment
High-Scale Processing
Flexible Scheduling

On the other hand, RabbitMQ provides the following key features:

Robust messaging for applications
Easy to use
Runs on all major operating systems

RabbitMQ is an open source tool with 5.95K GitHub stars and 1.78K GitHub forks. Here's a link to RabbitMQ's open source repository on GitHub.

IronWorker vs RabbitMQ