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

ActiveMQ

610
1.3K
+ 1
77
Apollo

2.4K
1.8K
+ 1
25
Add tool

ActiveMQ vs Apollo: What are the differences?

Introduction

In this article, we will explore the key differences between ActiveMQ and Apollo, two popular messaging systems.

  1. Message Persistence: ActiveMQ stores messages in a journal or database using JDBC or file-based persistence. On the other hand, Apollo uses a database-backed message store that provides faster message persistence and recovery.

  2. Performance: ActiveMQ has limited scalability due to its use of Java Message Service (JMS) for communication. In contrast, Apollo is built on the Apache Foundation's NIO messaging support, allowing for higher performance and throughput.

  3. Protocols: ActiveMQ supports various protocols such as MQTT, STOMP, and WebSocket. Apollo primarily focuses on AMQP (Advanced Message Queuing Protocol) but also supports MQTT, STOMP, and HTTP.

  4. Configuration: ActiveMQ uses XML-based configuration, which can be complex and hard to manage. In contrast, Apollo uses a simple and flexible configuration file format that allows for easier setup and maintenance.

  5. Transports: ActiveMQ uses traditional TCP/IP-based transports for communication. Apollo, on the other hand, utilizes the WebSocket protocol, which enables real-time bidirectional communication between clients and servers over a single, long-lived connection.

  6. Clustering: ActiveMQ's clustering mechanism is primarily based on network connectors, which can be complex to configure and maintain. Apollo, on the other hand, provides a simpler and more flexible clustering mechanism using the concept of virtual hosts.

In summary, ActiveMQ and Apollo differ in terms of message persistence, performance, supported protocols, configuration, transports, and clustering mechanisms. These differences make each messaging system suitable for specific use cases based on requirements and preferences.

Manage your open source components, licenses, and vulnerabilities
Learn More
Pros of ActiveMQ
Pros of Apollo
  • 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
  • 12
    From the creators of Meteor
  • 8
    Great documentation
  • 3
    Open source
  • 2
    Real time if use subscription

Sign up to add or upvote prosMake informed product decisions

Cons of ActiveMQ
Cons of Apollo
  • 1
    ONLY Vertically Scalable
  • 1
    Support
  • 1
    Low resilience to exceptions and interruptions
  • 1
    Difficult to scale
  • 1
    File upload is not supported
  • 1
    Increase in complexity of implementing (subscription)

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

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

What companies use ActiveMQ?
What companies use Apollo?
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 Apollo?

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

Blog Posts

What are some alternatives to ActiveMQ and Apollo?
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.
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.
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.
See all alternatives