Publisher-based message data caching in a publish-subscription environment

• US 9,537,970 B2
• Filed: 10/30/2014
• Issued: 01/03/2017
• Est. Priority Date: 02/23/2011
• Status: Active Grant

• Current Assignee: Kyndryl Incorporated (Kyndryl Holdings, Inc.)
• Original Assignee: International Business Machines Corporation
• Inventors: Bhogal, Kulvir S., Gale, Martin J., Hamilton, Rick A. II, Jones, Andrew R., O'Connell, Brian M.
• Primary Examiner(s): Coulter, Kenneth R
• Application Number:
  US14/528,469
• Publication Number:
  US 20150052194A1
• Time in Patent Office: 796 Days
• Field of Search: 709/246, 709/235, 709/234, 709204-206
• US Class Current: 1/1
• CPC Class Codes: G06F 9/542 Event management; Broadcasting; Multicasting; Notifications
• CPC Class Codes: H04L 12/1859 adapted to provide push services, e.g. data channels
• CPC Class Codes: H04L 51/18 Commands or executable codes
• CPC Class Codes: H04L 67/562 Brokering proxy services
• CPC Class Codes: H04L 67/568 Storing data temporarily at an intermediate stage, e.g. caching

Abstract

Embodiments of the present invention provide an approach for a broker-assisted, publisher side cache that can be utilized to reduce a volume of data (e.g., network traffic) delivered between a publisher and broker in a publication/subscription (pub/sub) environment. Specifically, in a typical embodiment, when a message is received on a broker system from a publisher system, the broker system analyzes the message for potentially repetitive data. Such data can be determined from historical messages (e.g., determining that a certain set of data appeared in multiple messages and is thus flagged in a database or the like), a set of rules (e.g., if data set “Y” appears, flag it as potentially repetitive), etc. Regardless, once such a set of data has been identified, a unique identifier/key corresponding thereto will be sent back to the publisher system and the set of data will be stored in a (data) cache. Upon receipt, the publisher system will cache/store the unique identifier in a (key) cache. Then, when the publisher system generates a future message that would contain the same set of data, the publisher system will substitute the unique identifier (as retrieved from the key cache) for the set of data to yield an abbreviated/truncated message. The abbreviated message would be sent to the broker system, which would: analyze the message; locate the unique identifier; retrieve the corresponding set of data from the (data) cache; replace the unique identifier with the set of data to yield a completed message; and then send the completed message to relevant subscriber system(s).

Claims

1. A computer-implemented method for caching potentially repetitive message data in a publish-subscription (pub/sub) messaging environment, comprising:

determining that a first type of message has a publication rate higher than other types of messages;

identifying a set of data in a first message received on a broker system from a publisher system, the set of data having a potential to appear in at least one future message based on the publication rate, wherein the first message is of the first type;

sending a unique identifier corresponding to the set of data from the broker system to the publisher system, the unique identifier identifying the set of data as cacheable;

receiving a second message on the broker system from the publisher system, the second message having the unique identifier;

retrieving the set of data from a cache;

replacing the unique identifier in the second message with the set of data to yield a completed message;

sending the completed message to a subscriber system;

determining that a second type of message has a higher publication rate than other types of messages, the higher publication rate surpassing the publication rate of the first type of message; and

invalidating the set of data from the cache in response to the determination that the second type of message has the higher publication rate than other types of messages.

2. The computer-implemented method of claim 1, further comprising the broker system caching the set of data.

3. The computer-implemented method of claim 1, further comprising:

the publisher system receiving the unique identifier; and

the publisher system caching the unique identifier.

4. The computer-implemented method of claim 3, further comprising:

the publisher system identifying data in a new message to be generated as the set of data;

the publisher system generating the second message with the unique identifiers appearing in the second message in place of the set of data; and

the publisher system sending the second message to the broker system.

5. The computer-implemented method of claim 1, the potential being identified based on an appearance of the set of data in at least one message received prior to the first message.

6. The computer-implemented method of claim 1, the broker system, the publisher system, and the subscriber system each being computerized systems in the pub/sub messaging environment.

7. The computer-implemented method of claim 1, the broker system, the publisher system, and the subscriber system communicating over at least one type of computer network.

8. The computer-implemented method of claim 1, wherein a service solution provider provides a computer infrastructure that performs the method for one or more consumers.

9. A system for caching potentially repetitive message data in a publish-subscription (pub/sub) messaging environment, comprising:

a first bus;

a first processor coupled to the first bus; and

a first memory medium coupled to the first bus, the first memory medium comprising instructions to;

determine that a first type of message has a publication rate higher than other types of messages;

identify a set of data in a first message received on a broker system from a publisher system, the set of data having a potential to appear in at least one future message based on the publication rate, wherein the first message is of the first type;

send a unique identifier corresponding to the set of data from the broker system to the publisher system, the unique identifier identifying the set of data as cacheable;

receive a second message on the broker system from the publisher system, the second message having the unique identifier;

retrieve the set of data from a cache;

replace the unique identifier in the second message with the set of data to yield a completed message;

send the completed message to a subscriber system;

determine that a second type of message has a higher publication rate than other types of messages, the higher publication rate surpassing the publication rate of the first type of message; and

invalidate the set of data from the cache in response to the determination that the second type of message has the higher publication rate than other types of messages.

10. The system of claim 9, the first memory medium further comprising instructions to cache the set of data on the broker system.

11. The system of claim 9, further comprising:

a second bus;

a second processor coupled to the second bus; and

a second memory medium coupled to the second bus, the second memory medium comprising instructions to;

receive the unique identifier; and

cache the unique identifier on the publisher system.

12. The system of claim 11, the second memory medium further comprising instructions to:

identify data in a new message to be generated as the set of data;

generate the second message with the unique identifiers appearing in the second message in place of the set of data; and

send the second message to the broker system.

13. The system of claim 9, the broker system, the publisher system, and the subscriber system each being computerized systems in the pub/sub messaging environment.

14. The system of claim 9, the broker system, the publisher system, and the subscriber system communicating over at least one type of computer network.

15. At least one computer program product for caching potentially repetitive message data in a publish-subscription (pub/sub) messaging environment, the at least one computer program product comprising at least one computer readable storage media, and program instructions stored on the at least one computer readable storage media, to:

determine that a first type of message has a publication rate higher than other types of messages;

identify a set of data in a first message received on a broker system from a publisher system, the set of data having a potential to appear in at least one future message based on the publication rate, wherein the first message is of the first type;

send a unique identifier corresponding to the set of data from the broker system to the publisher system, the unique identifier identifying the set of data as cacheable;

receive a second message on the broker system from the publisher system, the second message having the unique identifier;

retrieve the set of data from a cache;

replace the unique identifier in the second message with the set of data to yield a completed message;

send the completed message to a subscriber system;

determine that a second type of message has a higher publication rate than other types of messages, the higher publication rate surpassing the publication rate of the first type of message; and

invalidate the set of data from the cache in response to the determination that the second type of message has the higher publication rate than other types of messages.

16. The at least one computer program product of claim 15, further comprising program instructions stored on the at least one computer readable storage media to cache the set of data on the broker system.

17. The at least one computer program product of claim 15, further comprising program instructions stored on the at least one computer readable storage media to:

receive the unique identifier on the publisher system; and

cache the unique identifier on the publisher system.

18. The at least one computer program product of claim 17 further comprising program instructions stored on the at least one computer readable storage media to:

identify data in a new message to be generated as the set of data on the publisher system;

generate the second message with the unique identifiers appearing in the second message in place of the set of data on the publisher system; and

send the second message to the broker system from the publisher system.

19. The at least one computer program product of claim 15, the broker system, the publisher system, and the subscriber system each being computerized systems in the pub/sub messaging environment.

20. The at least one computer program product of claim 15, the broker system, the publisher system, and the subscriber system communicating over at least one type of computer network.