Messaging

JMS

Jakarta Messaging (formerly Java Message Service)

Caution Formal standard Eclipse Foundation (Jakarta EE); originally JCP Since 2001

Judgement: Caution

Java-only messaging API; maintain if you have it, don't pick it new.

Java API specification for producing, sending, and consuming messages between application components. Originally JSR 914 under the Java Community Process; now Jakarta Messaging under the Eclipse Foundation.

Implemented by ActiveMQ, Artemis, IBM MQ, Solace, and most enterprise message brokers. JMS sits one layer above wire protocols like AMQP — it standardises the application API rather than the on-the-wire bytes.

At a glance

Category
Messaging
Governance
Eclipse Foundation (Jakarta EE); originally JCP
Status
Stable; Jakarta Messaging 3.1 is current
First released
2001

Links

Related standards

Other standards in Messaging.

See JMS in context

Open the interactive Data Landscape to compare JMS against every other open standard, or grab the raw JSON. Spotted something wrong? Open an issue.