Parallel message processing on diverse messaging buses

• US 9,426,114 B2
• Filed: 10/29/2013
• Issued: 08/23/2016
• Est. Priority Date: 10/29/2013
• Status: Active Grant

• Current Assignee: Red Hat, Inc. (International Business Machines Corporation)
• Original Assignee: Red Hat, Inc. (International Business Machines Corporation)
• Inventors: Nguyen, Filip, Balent, Robert
• Primary Examiner(s): Gillis, Brian J
• Assistant Examiner(s): Guzman, Javier O
• Application Number:
  US14/066,309
• Publication Number:
  US 20150120853A1
• Time in Patent Office: 1,029 Days
• Field of Search: 709/207
• US Class Current: 1/1
• CPC Class Codes: H04L 51/226 Delivery according to priorities

Abstract

Systems, methods, and techniques are disclosed for processing messages using a messaging bus. An example system includes an input queue that stores one or more input messages and an output queue that stores one or more output messages. The example system also includes a first service residing in a first messaging bus. In a composite transaction, the first service processes a first message and generates a second message in accordance with processing the first message. The example system further includes a transaction manager that places the second message in the output queue. The second message is routed from the output queue to a second service residing in a second messaging bus for processing, and the first and second messaging buses are diverse. The second service processes, during the composite transaction, the second message.

Claims

1. A system for processing messages using a messaging bus, the system comprising:

a first messaging bus including a first service and a first transaction manager, wherein the first service is coupled to an input queue and an output queue, and a composite transaction includes a first sub-transaction and a second sub-transaction, wherein in the composite transaction, the first service processes a first message from the input queue and generates a second message in accordance with processing the first message, and wherein the first transaction manager places the second message in the output queue, and the second message is routed from the output queue to a second service for processing;

a second messaging bus including the second service and a second transaction manager, wherein the second messaging bus is diverse from the first messaging bus and processes, during the composite transaction, the second message; and

a topic queue that accepts subscriptions from a plurality of services residing on diverse messaging buses, wherein the first transaction manager subscribes the first service to the topic queue and the second transaction manager subscribes the second service to the topic queue,

wherein in response to successful processing of the first message, the first service commits the first sub-transaction and the transaction manager publishes to the topic queue a third message indicating that the first service has committed the first sub-transaction, and

wherein in response to receiving the third message indicating that the first sub-transaction has been committed and in response to successful processing of the second message, the second transaction manager sends an indication to the second service to commit the second sub-transaction.

2. The system of claim 1, wherein a time period in which the first service processes the first message overlaps with a time period in which the second service processes the second message, and wherein in response to the indication to commit the second sub-transaction, the second service commits the second sub-transaction.

3. The system of claim 1, wherein the processing of the first message entails performing the first sub-transaction of the composite transaction, and the processing of the second message entails performing the second sub-transaction of the composite transaction, and wherein the second service initiates processing the second message before the first service commits the first sub-transaction.

4. The system of claim 3,

wherein the first transaction manager publishes one or more messages to the topic queue, and the second transaction manager receives one or more messages from the topic queue.

5. The system of claim 4, wherein the first transaction manager copies the first message, and wherein in response to unsuccessful processing of the first message, the first transaction manager places the copy of the first message in the input queue, rolls back the first sub-transaction, and publishes to the topic queue a fourth message indicating that the first service has rolled back the first sub-transaction.

6. The system of claim 5,

wherein the second transaction manager determines a status of the first sub-transaction in accordance with one or more messages published to the topic queue, and

wherein in response to receiving the fourth message indicating that the first sub-transaction has been rolled back, the second transaction manager rolls back the second sub-transaction and discards the second message.

7. The system of claim 1, wherein the first and second messaging buses have different messaging architectures.

8. The system of claim 1, wherein the first and second messaging buses have the same messaging architecture.

9. The system of claim 6, wherein in response to unsuccessful processing of the second message, the second transaction manager rolls back the second sub-transaction and places the second message in the output queue of the first service.

10. A method of processing messages using a messaging bus, the method comprising:

processing, by a first service residing in a first messaging bus, a first message from an input queue;

generating a second message in accordance with processing the first message;

placing the second message in an output queue, wherein the second message is routed from the output queue to a second service for processing, wherein the second service resides in a second messaging bus diverse from the first messaging bus, and wherein a composite transaction includes a first sub-transaction and a second sub-transaction, and in the composite transaction, the first service processes the first message and the second service processes the second message;

subscribing, by a first transaction manager, the first service to a topic queue that accepts subscriptions from a plurality of services residing on diverse messaging buses;

subscribing, by a second transaction manager, the second service to the topic queue;

in response to successful processing of the first message, committing the first sub-transaction and publishing to the topic queue a third message indicating that the first service has committed the first sub-transaction; and

in response to receiving the third message indicating that the first sub-transaction has been committed and in response to successful processing of the second message, sending, by the second transaction manager, an indication to the second service to commit the second sub-transaction.

11. The method of claim 10, wherein the first service processes the first message and the second service processes the second message in parallel.

12. The method of claim 10, wherein the first service processes the first message in the first sub-transaction of the composite transaction, the second service processes the second message in the second sub-transaction of the composite transaction, and the second service initiates processing of the second message before the first service commits the first sub-transaction.

13. The method of claim 10, further including:

when processing of the first message is successful;

committing the first sub-transaction of the composite transaction; and

publishing to the topic queue a third message indicating that the first sub-transaction has been committed.

14. The method of claim 10, further including:

copying the first message; and

in response to unsuccessful processing of the first message;

placing the copy of the first message in the input queue;

rolling back the first sub-transaction; and

publishing to the topic queue a fourth message indicating that the first sub-transaction has been has rolled back.

15. The method of claim 14, further including:

generating a unique transaction identifier for the composite transaction;

identifying a current time at which processing of the composite transaction is initiated;

augmenting the first message to include the unique transaction identifier and current time, wherein the first service processes the first message by processing the augmented message;

augmenting the second message to include the unique transaction identifier and current time, wherein the placing the second message in an output queue includes placing the augmented second message in the output queue, and wherein the publishing to the topic queue the fourth message includes publishing to the topic queue the unique transaction identifier and the current time.

16. The method of claim 15, further including:

listening, by the second transaction manager, to messages published to the topic queue;

determining a status of the first sub-transaction in accordance with one or more messages published to the topic queue;

in response to the indication to commit the second sub-transaction, committing, by the second service, the second sub-transaction;

in response to receiving the fourth message indicating that the first sub-transaction has been rolled back, rolling back the second sub-transaction and discarding the second message; and

in response to unsuccessful processing of the second message, rolling back the second sub-transaction and placing the second message in the output queue of the first service.

17. The method of claim 16, further including:

in response to the status of the first sub-transaction not yet having been determined in accordance with the one or more messages in the topic queue, waiting for the status of the first sub-transaction to be determined.

18. The method of claim 16, wherein the subscribing the second service occurs at a second current time, the method further including:

determining whether the second current time is subsequent to the first current time; and

in response to the second current time being subsequent to the first current time, placing the second message in the output queue of the first service without processing the second message.

19. A non-transitory machine-readable medium comprising a plurality of machine-readable instructions that when executed by one or more processors is adapted to cause the one or more processors to perform a method comprising:

processing, by a first service residing in a first messaging bus, a first message from an input queue;

generating a second message in accordance with processing the first message;

placing the second message in an output queue, wherein the second message is routed from the output queue to a second service for processing, wherein the second service resides in a second messaging bus diverse from the first messaging bus, and wherein in a composite transaction includes a first sub-transaction and a second sub-transaction, and in the composite transaction, the first service processes the first message and the second service processes the second message;

subscribing, by a first transaction manager, the first service to a topic queue that accepts subscriptions from a plurality of services residing on diverse messaging buses;

subscribing, by a second transaction manager, the second service to the topic queue;

in response to successful processing of the first message, committing the first sub-transaction and publishing to the topic queue a third message indicating that the first service has committed the first sub-transaction; and

in response to receiving the third message indicating that the first sub-transaction has been committed and in response to successful processing of the second message, sending, by the second transaction manager, an indication to the second service to commit the second sub-transaction.

20. The non-transitory machine-readable medium of claim 19, wherein a time period in which the first message is processed overlaps with a time period in which the second message is processed.