What is Sandglass?
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.
Sandglass is a tool in the Message Queue category of a tech stack.
Sandglass is an open source tool with 1.5K GitHub stars and 45 GitHub forks. Here’s a link to Sandglass's open source repository on GitHub
Who uses Sandglass?
Python, Node.js, Java, Ruby, and Go are some of the popular tools that integrate with Sandglass. Here's a list of all 5 tools that integrate with Sandglass.
Pros of Sandglass
Be the first to leave a pro
- Horizontal scalability
- Highly available
- Persistent storage
- Time ordered
- Multiple consumers per group for a partition
- Produce message to be consumed in the future
- Acknowledge/NotAcknowledge each message individually
- Automatic redelivery and commit offset tracking
- Language agnostic
Sandglass Alternatives & Comparisons
What are some alternatives to Sandglass?
See all alternatives
RabbitMQ gives your applications a common platform to send and receive messages, and your messages a safe place to live until received.
Kafka is a distributed, partitioned, replicated commit log service. It provides the functionality of a messaging system, but with a unique design.
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.
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.
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.