Need advice about which tool to choose?Ask the StackShare community!

Disque

10
23
+ 1
0
Sandglass

1
6
+ 1
0
Add tool

Disque vs Sandglass: What are the differences?

Disque: In-memory, distributed job queue. Disque is an ongoing experiment to build a distributed, in-memory, message broker. Its goal is to capture the essence of the "Redis as a jobs queue" use case, which is usually implemented using blocking list operations, and move it into an ad-hoc, self-contained, scalable, and fault tolerant design, with simple to understand properties and guarantees, but still resembling Redis in terms of simplicity, performance, and implementation as a C non-blocking networked server; 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.

Disque and Sandglass belong to "Message Queue" category of the tech stack.

Disque and Sandglass are both open source tools. It seems that Disque with 7.37K GitHub stars and 516 forks on GitHub has more adoption than Sandglass with 1.52K GitHub stars and 40 GitHub forks.

Get Advice from developers at your company using Private StackShare. Sign up for Private StackShare.
Learn More

Sign up to add or upvote prosMake informed product decisions

Sign up to add or upvote consMake informed product decisions

What is Disque?

Disque is an ongoing experiment to build a distributed, in-memory, message broker. Its goal is to capture the essence of the "Redis as a jobs queue" use case, which is usually implemented using blocking list operations, and move it into an ad-hoc, self-contained, scalable, and fault tolerant design, with simple to understand properties and guarantees, but still resembling Redis in terms of simplicity, performance, and implementation as a C non-blocking networked server.

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.

Need advice about which tool to choose?Ask the StackShare community!

What companies use Disque?
What companies use Sandglass?
    No companies found
    See which teams inside your own company are using Disque or Sandglass.
    Sign up for Private StackShareLearn More

    Sign up to get full access to all the companiesMake informed product decisions

    What tools integrate with Disque?
    What tools integrate with Sandglass?
      No integrations found

      Sign up to get full access to all the tool integrationsMake informed product decisions

      What are some alternatives to Disque and Sandglass?
      RabbitMQ
      RabbitMQ gives your applications a common platform to send and receive messages, and your messages a safe place to live until received.
      Kafka
      Kafka is a distributed, partitioned, replicated commit log service. It provides the functionality of a messaging system, but with a unique design.
      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.
      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.
      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.
      See all alternatives