RabbitMQ vs SockJS

Overview

RabbitMQ

Stacks21.8K

Followers18.9K

Votes558

GitHub Stars13.2K

Forks4.0K

SockJS

Stacks27

Followers60

Votes0

GitHub Stars2.1K

Forks306

RabbitMQ vs SockJS: What are the differences?

### Comparison between RabbitMQ and SockJS

RabbitMQ and SockJS are both widely used messaging technologies, but they have distinct differences that make each suitable for specific use cases.

1. **Protocol**: RabbitMQ is an open-source message broker software that uses the Advanced Message Queuing Protocol (AMQP) for message transmission, while SockJS is a JavaScript library that provides a WebSocket emulation for real-time web applications.
   
2. **Message Routing**: RabbitMQ allows for complex message routing patterns with topics, headers, and direct exchanges, providing flexibility in message delivery. In contrast, SockJS focuses primarily on providing a seamless WebSocket connection between the client and server, with less emphasis on message routing.

3. **Persistent Messaging**: RabbitMQ offers durable queues and message persistence, ensuring that messages are not lost even in the case of sudden failures. SockJS does not inherently provide persistent messaging capabilities, which can be a crucial factor in certain applications that require message reliability.

4. **Concurrency Handling**: RabbitMQ supports high levels of concurrency and scalability through features like clustering and distributed message queuing. On the other hand, SockJS may not be as efficient in handling massive concurrent connections and may require additional resources for scaling.

5. **Compatibility**: RabbitMQ is compatible with various programming languages and platforms, making it a versatile choice for integrating messaging systems across different technologies. In comparison, SockJS is more focused on web-based applications and may not be as suitable for broader system integration.

6. **Delivery Guarantees**: RabbitMQ ensures reliable message delivery through acknowledgments and delivery guarantees, which can be crucial for critical messaging scenarios. SockJS, while efficient in real-time communication, may not provide the same level of robustness in message delivery assurance.

In Summary, RabbitMQ and SockJS offer distinct functionalities in messaging technologies, catering to different use cases based on requirements such as protocol support, message routing, persistence, concurrency handling, compatibility, and delivery guarantees.

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, SockJS

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

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

mediafinger

Feb 13, 2019

Reviewon

Kafka

RabbitMQ

The question for which Message Queue to use mentioned "availability, distributed, scalability, and monitoring". I don't think that this excludes many options already. I does not sound like you would take advantage of Kafka's strengths (replayability, based on an even sourcing architecture). You could pick one of the AMQP options.

I would recommend the RabbitMQ message broker, which not only implements the AMQP standard 0.9.1 (it can support 1.x or other protocols as well) but has also several very useful extensions built in. It ticks the boxes you mentioned and on top you will get a very flexible system, that allows you to build the architecture, pick the options and trade-offs that suite your case best.

For more information about RabbitMQ, please have a look at the linked markdown I assembled. The second half explains many configuration options. It also contains links to managed hosting and to libraries (though it is missing Python's - which should be Puka, I assume).

159k views159k

Comments

Detailed Comparison

RabbitMQ	SockJS
RabbitMQ gives your applications a common platform to send and receive messages, and your messages a safe place to live until received.	It gives you a coherent, cross-browser, Javascript API which creates a low latency, full duplex, cross-domain communication channel between the browser and the web server, with WebSockets or without.
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	-
Statistics
GitHub Stars 13.2K	GitHub Stars 2.1K
GitHub Forks 4.0K	GitHub Forks 306
Stacks 21.8K	Stacks 27
Followers 18.9K	Followers 60
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	No community feedback yet

What are some alternatives to RabbitMQ, SockJS?

Kafka

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

Underscore

A JavaScript library that provides a whole mess of useful functional programming helpers without extending any built-in objects.

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.

Deno

It is a secure runtime for JavaScript and TypeScript built with V8, Rust, and Tokio.

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.

Related Comparisons

RabbitMQ vs SockJS: What are the differences?

### Comparison between RabbitMQ and SockJS

RabbitMQ and SockJS are both widely used messaging technologies, but they have distinct differences that make each suitable for specific use cases.

1. **Protocol**: RabbitMQ is an open-source message broker software that uses the Advanced Message Queuing Protocol (AMQP) for message transmission, while SockJS is a JavaScript library that provides a WebSocket emulation for real-time web applications.
   
2. **Message Routing**: RabbitMQ allows for complex message routing patterns with topics, headers, and direct exchanges, providing flexibility in message delivery. In contrast, SockJS focuses primarily on providing a seamless WebSocket connection between the client and server, with less emphasis on message routing.

3. **Persistent Messaging**: RabbitMQ offers durable queues and message persistence, ensuring that messages are not lost even in the case of sudden failures. SockJS does not inherently provide persistent messaging capabilities, which can be a crucial factor in certain applications that require message reliability.

4. **Concurrency Handling**: RabbitMQ supports high levels of concurrency and scalability through features like clustering and distributed message queuing. On the other hand, SockJS may not be as efficient in handling massive concurrent connections and may require additional resources for scaling.

5. **Compatibility**: RabbitMQ is compatible with various programming languages and platforms, making it a versatile choice for integrating messaging systems across different technologies. In comparison, SockJS is more focused on web-based applications and may not be as suitable for broader system integration.

6. **Delivery Guarantees**: RabbitMQ ensures reliable message delivery through acknowledgments and delivery guarantees, which can be crucial for critical messaging scenarios. SockJS, while efficient in real-time communication, may not provide the same level of robustness in message delivery assurance.

In Summary, RabbitMQ and SockJS offer distinct functionalities in messaging technologies, catering to different use cases based on requirements such as protocol support, message routing, persistence, concurrency handling, compatibility, and delivery guarantees.

RabbitMQ vs SockJS

Overview

RabbitMQ vs SockJS: What are the differences?

Share your Stack

Advice on RabbitMQ, SockJS

Detailed Comparison

What are some alternatives to RabbitMQ, SockJS?

Kafka

Underscore

Celery

Amazon SQS

NSQ

Deno

ActiveMQ

ZeroMQ

Apache NiFi

Gearman

Related Comparisons

Bootstrap vs Materialize

Django vs Laravel vs Node.js

Bootstrap vs Foundation vs Material UI

Node.js vs Spring-Boot

Flyway vs Liquibase

RabbitMQ vs SockJS

Overview

RabbitMQ vs SockJS: What are the differences?

Share your Stack

Advice on RabbitMQ, SockJS

Detailed Comparison

What are some alternatives to RabbitMQ, SockJS?

Kafka

Underscore

Celery

Amazon SQS

NSQ

Deno

ActiveMQ

ZeroMQ

Apache NiFi

Gearman

Related Comparisons

Bootstrap vs Materialize

Django vs Laravel vs Node.js

Bootstrap vs Foundation vs Material UI

Node.js vs Spring-Boot

Flyway vs Liquibase