JAVA MESSAGE SERVICE (JMS)

Java solution for messaging systems, key features are:

• only-once, at-most-once semantics support
• Decoupling in time thanks to durable destinations
• Possibility of non-blocking reception via listeners
• Messages sent within a session (via a given Session object) towards the same destination benefit from in-order delivery property

VENDOR AGNOSTIC

JMS is independent from specific vendor solution and allow the application to interact with them in a transparent way

flowchart TD
A[java application]
B[JMS API]
C[JMS provider]
D[JMS provider]
E[JMS provider]
F[IBM MQ series]
G[Progress sonic MQ]
H[Fiorano]
A --> B
B --> C & D & E
C --> F
D --> G
E --> H

RELIABILITY in JMS

reliability is handled trough ACK messages that are given from the JMS broker to the publisher and from the consumer to the broker

flowchart LR
A[publisher]
B{broker}
C[consumer]
D[(persistent\n storage)]
A --1 publish--> B
B --2 saves--> D
B --3 ack message--> A
B --4 consume--> C
C --5 ack message--> B

ACKS can be of 3 different types:

• lazy
• automatic
• client side

JMS allow to specify store semantics of a message:

• PERSISTENT messages are guaranteed that are saved at the JMS provider side
• NON_PERSISTENT messages are not saved on persistent storage

PREVIOUS NEXT