Home
Application and Data
Data Stores
Message Queue

Disque vs VerneMQ

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

Disque
11
25
+ 1
0
VerneMQ
31
136
+ 1
6
Add tool

Disque vs VerneMQ: What are the differences?

Developers describe Disque as "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. On the other hand, VerneMQ is detailed as "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..

Disque and VerneMQ can be primarily classified as "Message Queue" tools.

Disque and VerneMQ are both open source tools. Disque with 7.37K GitHub stars and 516 forks on GitHub appears to be more popular than VerneMQ with 1.76K GitHub stars and 189 GitHub forks.

Manage your open source components, licenses, and vulnerabilities
Learn More
Pros of Disque
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

    - No public GitHub repository available -

    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 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!

    Jobs that mention Disque and VerneMQ as a desired skillset
    Senior Software Engineer, Big Data
    Pinterest
    San Francisco, CA, US; , CA, US
    View Job Details
    DreamTrinoAirflow+11
    Staff Software Engineer - Site Reliability
    Pinterest
    Toronto, ON, CA
    View Job Details
    SpeedDreamLinux+20
    Manager II, Engineering - Big Data Query Platform
    Pinterest
    San Francisco, CA, US; , US
    View Job Details
    DreamTrinoYarn+7
    Staff Software Engineer, Internal LLM Tooling
    Pinterest
    Toronto, ON, CA
    View Job Details
    LLMDreamTypeScript+8
    Backend Engineer, Data Pipeline
    LaunchDarkly
    Oakland, California, United States
    View Job Details
    EscapeGoogleage+10
    What companies use Disque?
    What companies use VerneMQ?
    Manage your open source components, licenses, and vulnerabilities
    Learn More

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

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

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

      What are some alternatives to Disque and VerneMQ?
      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.
      MySQL
      The MySQL software delivers a very fast, multi-threaded, multi-user, and robust SQL (Structured Query Language) database server. MySQL Server is intended for mission-critical, heavy-load production systems as well as for embedding into mass-deployed software.
      PostgreSQL
      PostgreSQL is an advanced object-relational database management system that supports an extended subset of the SQL standard, including transactions, foreign keys, subqueries, triggers, user-defined types and functions.
      MongoDB
      MongoDB stores data in JSON-like documents that can vary in structure, offering a dynamic, flexible schema. MongoDB was also designed for high availability and scalability, with built-in replication and auto-sharding.
      See all alternatives

      Related Comparisons

      Disque vs IronMQCloudAMQP vs DisqueDisque vs RabbitMQActiveMQ vs DisqueAmazon SQS vs Disque

      Trending Comparisons

      Django vs Laravel vs Node.jsBootstrap vs Foundation vs Material-UINode.js vs Spring BootFlyway vs LiquibaseAWS CodeCommit vs Bitbucket vs GitHub

      Top Comparisons

      Postman vs Swagger UIHipChat vs Mattermost vs SlackBitbucket vs GitHub vs GitLabBootstrap vs Materialize