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

ActiveMQ

607
1.3K
+ 1
77
Disque

11
25
+ 1
0
Add tool

ActiveMQ vs Disque: What are the differences?

Developers describe ActiveMQ as "A message broker written in Java together with a full JMS client". 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. On the other hand, Disque is detailed 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.

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

ActiveMQ and Disque are both open source tools. It seems that Disque with 7.37K GitHub stars and 516 forks on GitHub has more adoption than ActiveMQ with 1.5K GitHub stars and 1.05K GitHub forks.

Get Advice from developers at your company using StackShare Enterprise. Sign up for StackShare Enterprise.
Learn More
Pros of ActiveMQ
Pros of Disque
  • 18
    Easy to use
  • 14
    Open source
  • 13
    Efficient
  • 10
    JMS compliant
  • 6
    High Availability
  • 5
    Scalable
  • 3
    Distributed Network of brokers
  • 3
    Persistence
  • 3
    Support XA (distributed transactions)
  • 1
    Docker delievery
  • 1
    Highly configurable
  • 0
    RabbitMQ
    Be the first to leave a pro

    Sign up to add or upvote prosMake informed product decisions

    Cons of ActiveMQ
    Cons of Disque
    • 1
      ONLY Vertically Scalable
    • 1
      Support
    • 1
      Low resilience to exceptions and interruptions
    • 1
      Difficult to scale
      Be the first to leave a con

      Sign up to add or upvote consMake informed product decisions

      What is 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.

      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.

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

      What companies use ActiveMQ?
      What companies use Disque?
      See which teams inside your own company are using ActiveMQ or Disque.
      Sign up for StackShare EnterpriseLearn More

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

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

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

        Blog Posts

        What are some alternatives to ActiveMQ and Disque?
        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.
        Apollo
        Build a universal GraphQL API on top of your existing REST APIs, so you can ship new application features fast without waiting on backend changes.
        IBM MQ
        It is a messaging middleware that simplifies and accelerates the integration of diverse applications and business data across multiple platforms. It offers proven, enterprise-grade messaging capabilities that skillfully and safely move information.
        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.
        See all alternatives