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

Sandglass

1
6
+ 1
0
VerneMQ

30
129
+ 1
6
Add tool

Sandglass vs VerneMQ: 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; VerneMQ: VerneMQ is a distributed IoT/MQTT message broker. VerneMQ is a distributed MQTT message broker, implemented in Erlang/OTP It's open source, and Apache 2 licensed. VerneMQ implements the MQTT 3.1, 3.1.1 and 5.0 specifications..

Sandglass and VerneMQ 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, VerneMQ provides the following key features:

  • Open Source, Apache 2 licensed
  • QoS 0, QoS 1, QoS 2
  • MQTT v5.0 fully implemented

Sandglass and VerneMQ are both open source tools. VerneMQ with 1.76K GitHub stars and 189 forks on GitHub appears to be more popular than Sandglass with 1.52K GitHub stars and 40 GitHub forks.

Get Advice from developers at your company using StackShare Enterprise. Sign up for StackShare Enterprise.
Learn More
Pros of Sandglass
Pros of VerneMQ
    Be the first to leave a pro
    • 1
      Fully open source clustering
    • 1
      Proxy Protocol support
    • 1
      Open Source Plugin System
    • 1
      Open Source Message and Metadata Persistence
    • 1
      MQTT v5 implementation
    • 1
      Open source shared subscriptions

    Sign up to add or upvote prosMake informed product decisions

    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.

    What is VerneMQ?

    VerneMQ is a distributed MQTT message broker, implemented in Erlang/OTP. It's open source, and Apache 2 licensed. VerneMQ implements the MQTT 3.1, 3.1.1 and 5.0 specifications.

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

    What companies use Sandglass?
    What companies use VerneMQ?
      No companies found
      See which teams inside your own company are using Sandglass or VerneMQ.
      Sign up for StackShare EnterpriseLearn More

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

      What tools integrate with Sandglass?
      What tools integrate with VerneMQ?

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

      What are some alternatives to Sandglass and VerneMQ?
      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.
      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