RFAMQP vs. JMS: Key Differences Explained
Advertisement
This article breaks down the key differences between AMQP (Advanced Message Queuing Protocol) and JMS (Java Message Service) protocols.
AMQP vs. JMS: Feature by Feature
| Features | AMQP | JMS |
|---|---|---|
| Full Form | Advanced Message Queuing Protocol | Java Message Service |
| What is it? | • It provides a standard messaging protocol across all platforms. • It’s cross-platform and supports multiple languages/frameworks. • It’s an open standard for passing messages between applications or organizations. • It lets different systems (e.g., .NET/Java) interact by agreeing on message format at the wire level, similar to web services. | • It provides a messaging API specifically for Java platforms. • It’s primarily targeted at Java users. • It doesn’t define a message format; that’s handled by AMQP. |
| Message Format/Types | Messages should be transmitted in binary format. | Messages are transmitted in five different data types: BytesMessage, MapMessage, ObjectMessage, StreamMessage, and TextMessage. |
| Message Models | Direct, Fanout, Topic, Headers | P2P (Point to Point), Publish/Subscribe |
| Working | It is completely client (i.e., API) and server (i.e., broker) agnostic. Any AMQP-compatible client can talk to any other AMQP client. Only the API is specified. | All applications should adhere to the JMS API to communicate with each other. |
| Security | Supported (i.e., SASL). However, the specification doesn’t explicitly enforce security; implementation is left to the JMS provider. | Supported i.e.SASL specification does not support security and hence implementation is left with JMS provider. |
| Message Routing | Complex routing schemes are possible based on a routing key. This enables more complicated routing. | Based on destination matching criteria. These are based on hierarchical topics and client message selection filters. |
| Multicast/Distribution List | Topics (publish/subscribe), Fanout (transmit to all bound Rx queues) | topics (publish/subscribe) topics |
| Message Delivery QoS | Yes (exactly once delivery semantics of a session) • Persistent/non-persistent delivery modes • Message priorities • Only message Ack and no-ack modes defined | • Persistent delivery modes • Different message ack types • Message priorities |
| Peek Queue | No | Yes (QueueBrowser object) - Allows you to check if a message is available without receiving it. |
| Priority Based Messaging | Yes (10 priority levels) | Yes (10 priority levels) |
Key Takeaways
- AMQP: A wire-level protocol defining the format of messages passed between systems. It’s designed for interoperability between different platforms and languages. Think of it as a universal translator for messaging.
- JMS: A Java API (Application Programming Interface) for accessing message-oriented middleware. It provides a standard way for Java applications to create, send, and receive messages.
In simpler terms, AMQP defines how messages are formatted and transported, while JMS defines how Java applications interact with messaging systems.
Advertisement
