ZeroMQ vs Sparrow | What are the differences? | StackShare

Sparrow vs ZeroMQ

Overview

ZeroMQ

Stacks258

Followers586

Votes71

GitHub Stars10.6K

Forks2.5K

Sparrow

Stacks6

Followers11

Votes0

Sparrow vs ZeroMQ: What are the differences?

What is Sparrow? A really fast lightweight queue written in Ruby that speaks memcache. Sparrow keeps messages in memory, but persists them to disk, using Sqlite, when the queue is shutdown.

What is ZeroMQ? Fast, lightweight messaging library that allows you to design complex communication system without much effort. 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.

Sparrow and ZeroMQ can be primarily classified as "Message Queue" tools.

ZeroMQ is an open source tool with 5.33K GitHub stars and 1.57K GitHub forks. Here's a link to ZeroMQ's open source repository on GitHub.

🔥 Trending in Background Jobs on StackShare

Solid Queue Background Jobs

Database-backed active job backend

Try it View Docs Alternatives

Try

Advice on ZeroMQ, Sparrow

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

Bela Tibor

Technical Lead at Salt & Pepper

Mar 10, 2021

Review

This depends on your needs, but basically Kafka is the de-facto solution to go for. RabbitMQ, ZeroMQ or similar message queuing systems have their advantages too. Check for parallel consuming, in-flight queue (topic for Kafka) creation needs, consumer <-> message relations (how many consumers are interested in a message, all consumers are interested in all messages) etc...

65 views65

Comments

Detailed Comparison

ZeroMQ	Sparrow
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.	Sparrow keeps messages in memory, but persists them to disk, using Sqlite, when the queue is shutdown.
Connect your code in any language, on any platform.;Carries messages across inproc, IPC, TCP, TPIC, multicast.;Smart patterns like pub-sub, push-pull, and router-dealer.;High-speed asynchronous I/O engines, in a tiny library.;Backed by a large and active open source community.;Supports every modern language and platform.;Build any architecture: centralized, distributed, small, or large.;Free software with full commercial support.	-
Statistics
GitHub Stars 10.6K	GitHub Stars -
GitHub Forks 2.5K	GitHub Forks -
Stacks 258	Stacks 6
Followers 586	Followers 11
Votes 71	Votes 0
Pros & Cons
Pros 23 Fast 20 Lightweight 11 Transport agnostic 7 No broker required 4 Low level APIs are in C Cons 5 No message durability 3 Not a very reliable system - message delivery wise 1 M x N problem with M producers and N consumers	No community feedback yet

What are some alternatives to ZeroMQ, Sparrow?

Kafka

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

RabbitMQ

RabbitMQ gives your applications a common platform to send and receive messages, and your messages a safe place to live until received.

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.

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.