Apache ActiveMQ

Apache ActiveMQ
Name	Apache ActiveMQ
Title	Apache ActiveMQ
Developer	Apache Software Foundation
Released	2004
Latest release version	5.x / Artemis 2.x
Programming language	Java
Operating system	Cross-platform
Genre	Message-oriented middleware
License	Apache License 2.0

Apache ActiveMQ is an open-source message broker that implements messaging protocols to enable asynchronous communication between distributed applications. It provides enterprise-grade messaging features for integration between services, enabling decoupling of producers and consumers across heterogeneous environments. ActiveMQ is maintained by the Apache Software Foundation and has influenced messaging architectures in large-scale systems.

History

ActiveMQ originated in the early 2000s as part of the rise of enterprise integration patterns popularized by authors and projects such as Martin Fowler, Gregor Hohpe, Spring Framework, and Enterprise Integration Patterns. Development and stewardship moved under the Apache Software Foundation where ActiveMQ became a top-level project alongside efforts like Apache Camel, Apache ServiceMix, Apache Kafka, and Apache Helix. Over time, ActiveMQ versions evolved into two main lines: the "Classic" 5.x series and the Artemis reimplementation influenced by HornetQ and contributions from Red Hat engineers, aligning with projects such as WildFly, JBoss, GlassFish, and Tomcat. ActiveMQ has been adopted by organizations including Twitter, LinkedIn, NASA, Flickr, and many enterprises using stacks with Spring Boot, Hibernate, Apache Cassandra, and Oracle Database.

Architecture

ActiveMQ's architecture centers on broker-based message routing with pluggable components and transports. Core elements include brokers, destinations (queues and topics), persistence adapters, and network connectors; these relate to integration frameworks like Apache Camel, orchestration tools such as Kubernetes, and service meshes exemplified by Istio. ActiveMQ supports messaging models akin to standards from Java Message Service and interoperation with protocols such as AMQP, MQTT, STOMP, and OpenWire; this enables clients written for Java EE, Spring Framework, .NET Framework, Node.js, and Python to interoperate. Clustering, store-and-forward, and master/slave topologies integrate with storage systems like Apache Derby, LevelDB, PostgreSQL, and MySQL and with replication tools including Apache ZooKeeper and Raft.

Features

ActiveMQ implements transactional messaging, message selectors, durable subscriptions, and virtual topics, paralleling functionality in products such as IBM MQ, RabbitMQ, TIBCO, and Oracle WebLogic Server. It offers high-availability features — master/slave failover, network of brokers, and message persistence — compatible with backing stores like Apache Kafka integrations and with container orchestration through Docker. Monitoring and management integrate with Java Management Extensions, Prometheus, and Grafana dashboards, and with logging ecosystems including Log4j and Elastic Stack. Additional features include message grouping, advisory messages, scheduled delivery, and dead letter queues comparable to patterns implemented in Amazon SQS and Google Cloud Pub/Sub.

Installation and configuration

ActiveMQ distributions are provided as binaries and source, installable on platforms from Linux distributions like Debian and Red Hat Enterprise Linux to Microsoft Windows and macOS. Configuration is driven by XML and properties files and integrates with build and deployment tools such as Maven, Gradle, Ansible, and Terraform. For cloud-native deployment, ActiveMQ is packaged into containers orchestrated by Kubernetes and deployable on cloud providers including Amazon Web Services, Google Cloud Platform, and Microsoft Azure. Persistence configuration supports multiple stores including Apache Derby, LevelDB, and relational databases used by Oracle Database and PostgreSQL.

Clients and APIs

ActiveMQ provides client libraries and protocol bridges for a wide ecosystem: Java clients via Java Message Service APIs, .NET Framework clients via NMS, Python clients, Node.js libraries, and MQTT clients compatible with Eclipse Paho. Protocol adapters enable interoperability with AMQP implementations such as Qpid and with brokers like RabbitMQ and Apache Kafka via connectors. Integration with frameworks and middleware includes Spring Framework, Apache Camel, Hibernate, EJB containers in WildFly, and service integration in MuleSoft and Talend.

Use cases and deployments

Organizations employ ActiveMQ for enterprise integration, event-driven microservices, IoT message ingestion, and decoupled web application backends. Typical deployments include financial systems integrating with SWIFT gateways, telecommunications stacks interoperating with SIP infrastructure, telemetry pipelines used by NASA and research institutions, and real-time features in social platforms similar to early adopters like Flickr and Twitter. ActiveMQ is used alongside stream-processing frameworks such as Apache Storm, Apache Flink, and Apache Spark and paired with storage and search systems including Cassandra and Elasticsearch.

Security and administration

ActiveMQ supports SSL/TLS for secure transports, JAAS-based authentication, and role-based authorization compatible with identity providers and federated systems including LDAP, Active Directory, and OAuth 2.0 integrations in cloud platforms like Amazon Cognito and Okta. Administrative tooling includes the web console, JMX interfaces, and integration with monitoring systems such as Prometheus and Nagios. Hardening guidance draws on best practices from National Institute of Standards and Technology publications and common enterprise security controls applied in environments managed by teams using Ansible or Puppet.

Category:Message brokers