StackShareStackShare
Follow on
StackShare

Discover and share technology stacks from companies around the world.

Follow on

© 2025 StackShare. All rights reserved.

Product

  • Stacks
  • Tools
  • Feed

Company

  • About
  • Contact

Legal

  • Privacy Policy
  • Terms of Service
  1. Stackups
  2. Utilities
  3. Background Jobs
  4. Message Queue
  5. Sandglass vs Scheduler API

Sandglass vs Scheduler API

OverviewComparisonAlternatives

Overview

Sandglass
Sandglass
Stacks1
Followers6
Votes0
Scheduler API
Scheduler API
Stacks5
Followers16
Votes0

Sandglass vs Scheduler API: What are the differences?

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; Scheduler API: An API for scheduling queue messages. It is a simple API to delay SQS messages. Call our APIs and we'll publish your messages when you need them.

Sandglass and Scheduler API can be categorized as "Message Queue" tools.

Some of the features offered by Sandglass are:

  • Horizontal scalability
  • Highly available
  • Persistent storage

On the other hand, Scheduler API provides the following key features:

  • scheduling
  • cancelling scheduled SQS messages
  • changing the delay for already scheduled messages

Sandglass is an open source tool with 1.54K GitHub stars and 45 GitHub forks. Here's a link to Sandglass's open source repository on GitHub.

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)
or
Manual

Detailed Comparison

Sandglass
Sandglass
Scheduler API
Scheduler API

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.

It is a simple API to delay SQS messages. Call our APIs and we'll publish your messages when you need them.

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
scheduling ; cancelling scheduled SQS messages; changing the delay for already scheduled messages; checking the status of scheduled messages
Statistics
Stacks
1
Stacks
5
Followers
6
Followers
16
Votes
0
Votes
0
Integrations
Golang
Golang
Java
Java
Python
Python
Node.js
Node.js
Ruby
Ruby
No integrations available

What are some alternatives to Sandglass, Scheduler API?

Kafka

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

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

Celery

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

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

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

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

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

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

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

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.

Related Comparisons

Bootstrap
Materialize

Bootstrap vs Materialize

Laravel
Django

Django vs Laravel vs Node.js

Bootstrap
Foundation

Bootstrap vs Foundation vs Material UI

Node.js
Spring Boot

Node.js vs Spring-Boot

Liquibase
Flyway

Flyway vs Liquibase