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

ActiveMQ

614
1.3K
+ 1
77
Sandglass

1
6
+ 1
0
Add tool

ActiveMQ vs Sandglass: What are the differences?

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

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

ActiveMQ and Sandglass can be primarily classified as "Message Queue" tools.

ActiveMQ and Sandglass are both open source tools. Sandglass with 1.52K GitHub stars and 40 forks on GitHub appears to be more popular than ActiveMQ with 1.5K GitHub stars and 1.05K GitHub forks.

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

      - No public GitHub repository available -

      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 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 ActiveMQ?
      What companies use Sandglass?
        No companies found
        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 ActiveMQ?
        What tools integrate with Sandglass?

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

        Blog Posts

        What are some alternatives to ActiveMQ 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.
        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