Content aware routing of subscriptions for streaming and static data

• US 8,127,021 B2
• Filed: 03/14/2007
• Issued: 02/28/2012
• Est. Priority Date: 03/18/2006
• Status: Active Grant

• Current Assignee: Metafluent LLC
• Original Assignee: Metafluent LLC
• Inventors: Lankford, Peter, MacGaffey, Andrew
• Primary Examiner(s): Meky, Moustafa M
• Application Number:
  US12/225,044
• Publication Number:
  US 20090204712A1
• Time in Patent Office: 1,812 Days
• Field of Search: 709200-203, 709217-227, 709/228, 709/229
• US Class Current: 709/227
• CPC Class Codes: H04L 45/00 Routing or path finding of packets in data switching networks routing or path finding in wireless networks H04W40/00
• CPC Class Codes: H04L 45/24 Multipath
• CPC Class Codes: H04L 67/1001 for accessing one among a plurality of replicated servers
• CPC Class Codes: H04L 67/1008 based on parameters of servers, e.g. available memory or workload monitoring of computer activity G06F11/30
• CPC Class Codes: H04L 67/14 Session management for real-time applications in data packet communications networks H04L65/1066

Abstract

The invention relates to integration of streaming data, and more specifically relates to subscription routing: distributing the load of streaming data subscriptions across multiple servers in a session-oriented client-server architecture. In one embodiment the invention provides, in a client-server architecture, a method of implementing the client-side architecture whereby a logical connection and session may be mapped to one or more physical connections and sessions. The invention provides mobility of subscriptions from one physical session/connection to another based on directives from a server; and further permit a client to blend multiple physical subscriptions for different data streams into a single logical data stream based on directives from a server.

Claims

1. A computer readable medium having instructions stored thereon that, when executed by a processor on a first server, causes the processor to load-balance Java Message Service (JMS) requests, the instructions comprising:

receiving a JMS subscription request from a client, wherein the request comprises a topic name for a topic;

determining how to service the subscription request;

based on the determining, servicing the subscription request by generating one or more messages, wherein the one or more messages comprise one of;

a plurality of topic messages, a Redirection directive, or a Join directive; and

sending the one or more messages to the client;

wherein the Redirection directive comprises directing the client to send the subscription request to a second server;

wherein the Join directive comprises directing the client to generate a second subscription request to the second server, and in response receive a first part of the topic from the first server and a second part of the topic from the second server.

2. The computer readable medium of claim 1, wherein the determining how to service the subscription request is based on information received from the second server prior to the servicing the subscription request.

3. The computer readable medium of claim 2, wherein the information comprises load information of the second server.

4. The computer readable medium of claim 1, wherein the determining how to service the subscription request is based on an expected load of the topic.

5. The computer readable medium of claim 4, wherein the expected load of the topic comprises a preconfigured load or an heuristic load.

6. The computer readable medium of claim 1, wherein the determining how to service the subscription request is based on whether the topic can be split.

7. The computer readable medium of claim 1, wherein the determining how to service the subscription request is based on a Quality of Service of the topic that is designated for a particular requesting application or a user of the application.

8. The computer readable medium of claim 1, wherein the first part and the second part are joined at the client.

9. The computer readable medium of claim 1, wherein the Redirection directive comprises one or more from the following group:

a host name, a port number, a context name and the topic name.

10. The computer readable medium of claim 1, wherein the determining is in the form of logic that is pluggable in the first server.

11. The computer readable medium of claim 1, wherein the topic messages are generated from the first server using a first type of transport protocol, and are generated from the second server using a second transport protocol.

12. The computer readable medium of claim 11, where the first type of transport protocol comprises a direct feed that publishes via a multicast protocol, and the second type of transport protocol comprises a database-connected server that publishes via Transmission Control Protocol.

13. A computer implemented method for load-balancing Java Message Service (JMS) requests, the method comprising:

receiving a JMS subscription request from a client at a first server, wherein the request comprises a topic name for a topic;

determining how to service the request;

based on the determining, servicing the request by generating one or more messages, wherein the one or more messages comprise one of;

a plurality of topic messages, a Redirection directive, or a Join directive; and

sending the one or more messages to the client;

wherein the Redirection directive comprises directing the client to send the subscription request to a second server;

wherein the Join directive comprises directing the client to generate a second subscription request to the second server, and in response receive a first part of the topic from the first server and a second part of the topic from the second server.

14. The method of claim 13, wherein the determining how to service the request is based on information received from the second server prior to the servicing the request.

15. The method of claim 14, wherein the information comprises load information of the second server.

16. The method of claim 13, wherein the determining how to service the request is based on an expected load of the topic.

17. The method of claim 16, wherein the expected load of the topic comprises a preconfigured load or an heuristic load.

18. The method of claim 13, wherein the determining how to service the request is based on whether the topic can be split.

19. The method of claim 13, wherein the determining how to service the request is based on a Quality of Service of the topic that is designated for a particular requesting application or a user of the application.

20. The method of claim 13, wherein the first part and the second part are joined at the client.

21. The method of claim 13, wherein the Redirection directive comprises one or more from the following group:

a host name, a port number, a context name and the topic name.

22. The method of claim 13, wherein the determining is in the form of logic that is pluggable in the first server.

23. A system for load-balancing Java Message Service (JMS) requests, the system comprising:

a processor;

a computer readable medium coupled to the processor, wherein the computer readable medium stores instructions that cause the processor to perform the functionality of;

receiving a JMS subscription request from a client at a first server, wherein the request comprises a topic name for a topic;

determining how to service the request;

based on the determining, servicing the request by generating one or more messages, wherein the one or more messages comprise one of;

a plurality of topic messages, a Redirection directive, or a Join directive; and

sending the one or more messages to the client;

wherein the Redirection directive comprises directing the client to send the subscription request to a second server;

wherein the Join directive comprises directing the client to generate a second subscription request to the second server, and in response receive a first part of the topic from the first server and a second part of the topic from the second server.

24. The system of claim 23, wherein the determining how to service the request is based on information received from the second server prior to the servicing the subscription request.

25. The system of claim 23, wherein the information comprises load information of the second server.

26. The system of claim 23, wherein the determining how to service the request is based on an expected load of the topic.

27. The system of claim 26, wherein the expected load of the topic comprises a preconfigured load or an heuristic load.

28. The system of claim 23, wherein the determining how to service the request is based on whether the topic can be split.

29. The system of claim 23, wherein the first part and the second part are joined at the client.

30. The system of claim 23, wherein the Redirection directive comprises one or more from the following group:

a host name, a port number, a context name and the topic name.

31. The system of claim 23, wherein the determining how to service the subscription request is based on a Quality of Service of the topic that is designated for a particular requesting application or a user of the application.