Providing messages for a Java message service
Providing messages for Java message service (JMS) is disclosed. A described method includes determining timestamp information associated with a first Java™ message service (JMS) message. The timestamp information represents a time when the JMS message is either generated or received by a processing device. The method also includes determining destination information associated with the JMS message. The method further includes converting the JMS message into a first key-value data pair having a key data and a value data. The key data includes the timestamp information and the value data includes the destination information of the first JMS message.
1. A method comprising:
determining, by a processing device executing an application programming interface (API) stub, a timestamp information associated with a first JAVA™ message service (JMS) message, wherein the timestamp information represents a time when the JMS message is either generated by the processing device or received by the processing device;
determining, by the processing device executing the API stub, a destination information associated with the JMS message; and
converting the JMS message into a first key-value data pair comprising a key data and a value data, wherein the key data comprises the timestamp information and the value data comprises the destination information of the first JMS message.
2. The method of claim 1 further comprising sending the first key-value data pair to a JMS server.
3. The method of claim 2 wherein the first key-value data pair is sent to the JMS server as a storage request.
4. The method of claim 1 wherein the destination information is a JMS queue associated with the first key-value data pair.
5. The method of claim 1 wherein the destination information is a JMS topic associated with the first key-value data pair.
6. The method of claim 5 wherein the API stub subscribes to the JMS topic associated with the first key-value data pair.
7. The method of claim 6 further comprising receiving, by the processing device executing the API stub subscribed to the JMS topic, a second key value data pair, wherein the second key value data pair is a replicate of the first key value data pair.
8. The method of claim 7 further comprising converting the second key value data pair to a second JMS message, wherein the second JMS message is a replicate of the first JMS message.
9. A system comprising:
a memory;
a processing device to execute an application programming interface (API) stub, operatively coupled to the memory, to:
determine a timestamp information associated with a first JAVA™ message service (JMS) message, wherein the timestamp information represents a time when the JMS message is either generated by the processing device or received by the processing device;
determine a destination information associated with the JMS message; and
convert the JMS message into a first key-value data pair comprising a key data and a value data, wherein the key data comprises the timestamp information and the value data comprises the destination information of the first JMS message.
10. The system of claim 9 , wherein the processing device is to send the first key-value date pair to a JMS server as a storage request.
11. The system of claim 9 , wherein the destination information is one of a JMS queue or a JMS topic associated with the first key-value data pair.
12. The system of claim 11 wherein the API stub subscribes to the JMS topic associated with the first key-value data pair.
13. The system of claim 12 , wherein the processing device to execute the API stub subscribed to the JMS topic is to receive a second key value data pair, wherein the second key value data pair is a replicate of the first key value data pair.
14. The system of claim 13 , wherein the processing device is to convert the second key value data pair to a second JMS message, wherein the second JMS message is a replicate of the first JMS message.
15. A non-transitory machine-readable storage medium comprising instructions that, when accessed by a processing device to execute an application-programming interface (API) stub, cause the processing device to:
determine, by the processing device, a timestamp information associated with a first JAVA™ message service (JMS) message, wherein the timestamp information represents a time when the JMS message is either generated by the processing device or received by the processing device;
determine, by the processing device, a destination information associated with the JMS message; and
convert the JMS message into a first key-value data pair comprising a key data and a value data, wherein the key data comprises the timestamp information and the value data comprises the destination information of the first JMS message.
16. The non-transitory machine-readable storage medium of claim 15 , wherein the processing device is to send the first key-value date pair to a JMS server as a storage request.
17. The non-transitory machine-readable storage medium of claim 15 , wherein the destination information is one of a JMS queue or a JMS topic associated with the first key-value data pair.
18. The non-transitory machine-readable storage medium of claim 17 , wherein the API stub subscribes to the JMS topic associated with the first key-value data pair.
19. The non-transitory machine-readable storage medium of claim 18 , wherein the processing device to execute the API stub subscribed to the JMS topic is to receive a second key value data pair, wherein the second key value data pair is a replicate of the first key value data pair.
20. The non-transitory machine-readable storage medium of claim 19 , wherein the processing device is to convert the second key value data pair to a second JMS message, wherein the second JMS message is a replicate of the first JMS message.