# apache/activemq

Apache ActiveMQ

Repository: https://github.com/apache/activemq
Canonical: https://ross.abutalabs.com/products/activemq
Homepage: https://activemq.apache.org
Language: Java
License: Apache-2.0
License Family: permissive
Topics: activemq, java, amqp, amqps, apache, broker, jms, messaging, mqtt, openwire, stomp
Last push: 2026-08-26T06:09:40+00:00

## Health v2 (maintenance only)
Score: 98/100 (v2, computed 2026-09-03T02:20:16.233290+00:00)
- activity 99, release rhythm 96, longevity 100
- inputs: {"age_days": 6314, "days_push": 7, "days_rel": 27, "gap_med": 0, "n_releases_24m": 18}
- flags: none
- formula: round(0.45*activity + 0.35*rhythm + 0.20*longevity); archived -> min(score, 10)

## Adoption (not part of the score)
Stars 2451, forks 1494 (observed 2026-08-28T04:06:52.931768+00:00)

## What it is
Apache ActiveMQ is a high-performance, multi-protocol, Java-based open source message broker supporting JMS/Jakarta Messaging, AMQP, MQTT, STOMP, and HTTP/WS. It offers advanced features such as networks of brokers, load balancing, high availability via shared storage, scheduling, and persistence with KahaDB or JDBC.

## Use cases
- run a message broker for decoupling microservices
- exchange messages between web apps over STOMP over websockets
- integrate multi-platform applications using AMQP
- manage IoT devices via MQTT
- support existing JMS 1.1/2.0/Jakarta Messaging infrastructure
- distribute load across brokers with a network of brokers
- achieve high availability with shared storage master/slave brokers

## When to choose
- you need a mature, pluggable, multi-protocol Java message broker
- your stack relies on JMS or Jakarta Messaging APIs
- you need cross-language clients (JavaScript, C, C++, Python, .NET)
- you need broker clustering, load balancing, and HA
- you want Docker-deployable messaging infrastructure

## When to avoid
- you want the next-generation ActiveMQ codebase (consider ActiveMQ Artemis)
- you need a lightweight embedded queue without a full broker
- you are not on the JVM and prefer a simpler protocol-native broker
- you need Kafka-style high-throughput event streaming/log semantics

## Facets
- artifact type: service
- maturity: stable
- function: message-queue, middleware, networking, security
- domain: microservices, backend, iot, developer-tools
- platform: jvm, self-hosted, cross-platform
- tags: jms, amqp, mqtt, stomp, openwire, message-broker, apache, high-availability, persistence, kahadb, messaging, docker

## Member repositories
- apache/activemq (main) score 98

## Provenance
- Observed fields: from GitHub, fetched 2026-08-28T04:06:52.931768+00:00.
- Health v2: computed from the inputs above; adoption is never an input.
- Inferred fields (summary, facets, guidance): AI-extracted, prompt v1, taxonomy v1, on 2026-08-30T02:30:12.123586+00:00, confidence not recorded.
  - readme: https://github.com/apache/activemq (fetched 2026-08-28T04:06:52.931768+00:00, sha 94803c2765d6)
  - homepage: https://activemq.apache.org (fetched 2026-08-29T10:11:29.978683+00:00, sha aca02086123d)
  - site_page: https://activemq.apache.org/components/classic/documentation/jms2 (fetched 2026-08-29T10:11:29.988509+00:00, sha 1fc93e8637a9)
- Data as of 2026-08-30T08:39:29.467469+00:00.