Sandglass vs ZeroMQ: What are the differences?
What is Sandglass? Distributed, scalable, persistent time-sorted message queue. A distributed, horizontally scalable, persistent, time ordered message queue. Developed to support asynchronous tasks and message scheduling which makes it suitable for usage as a task queue.
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.
Sandglass and ZeroMQ can be primarily classified as "Message Queue" tools.
Some of the features offered by Sandglass are:
- Horizontal scalability
- Highly available
- Persistent storage
On the other hand, ZeroMQ provides the following key features:
- 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.
Sandglass and ZeroMQ are both open source tools. It seems that ZeroMQ with 5.33K GitHub stars and 1.57K forks on GitHub has more adoption than Sandglass with 1.52K GitHub stars and 40 GitHub forks.
What is Sandglass?
What is ZeroMQ?
Need advice about which tool to choose?Ask the StackShare community!
Why do developers choose Sandglass?
Sign up to add, upvote and see more prosMake informed product decisions
What are the cons of using Sandglass?
What companies use Sandglass?
Sign up to get full access to all the companiesMake informed product decisions
Sign up to get full access to all the tool integrationsMake informed product decisions
Our platform is based on interconnected services with a custom RPC protocol based on ZeroMQ and inspired by ZeroMQs LPP/MDP protocols.