End-to-end publish/subscribe middleware architecture
First Claim
1. An end-to-end publish/subscription messaging system with a middleware architecture, comprising:
- one or more messaging appliances configured to receive and route messages;
an interconnect utilizing channel-based messaging that routes messages over a first messaging layer based on one or more channels mapped to subscription topics, each of the one or more channels assigned to a communication pathway of a second messaging layer; and
a provisioning and management system linked via the interconnect to the one or more messaging appliances and configured to exchange administrative messages with each of the one or more messaging appliances,wherein each of the one or more messaging appliances is further configured to execute the routing of messages by dynamically selecting, in real time, a message transmission protocol and a message routing path.
1 Assignment
0 Petitions
Accused Products
Abstract
Message publish/subscribe systems are required to process high message volumes with reduced latency and performance bottlenecks. The end-to-end middleware architecture proposed by the present invention is designed for high-volume, low-latency messaging by, among other things, reducing intermediary hops with neighbor-based routing, introducing efficient native-to-external and external-to-native protocol conversions, monitoring system performance, including latency, in real time, employing topic-based and channel-based message communications, and dynamically optimizing system interconnect configurations and message transmission protocols.
-
Citations
43 Claims
-
1. An end-to-end publish/subscription messaging system with a middleware architecture, comprising:
-
one or more messaging appliances configured to receive and route messages; an interconnect utilizing channel-based messaging that routes messages over a first messaging layer based on one or more channels mapped to subscription topics, each of the one or more channels assigned to a communication pathway of a second messaging layer; and a provisioning and management system linked via the interconnect to the one or more messaging appliances and configured to exchange administrative messages with each of the one or more messaging appliances, wherein each of the one or more messaging appliances is further configured to execute the routing of messages by dynamically selecting, in real time, a message transmission protocol and a message routing path. - View Dependent Claims (2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17, 18, 19, 20, 21, 22, 23, 24, 25, 26, 27, 28, 29, 30, 31, 32, 33, 34, 35, 36, 37)
-
-
38. A system with a publish/subscribe middleware architecture, comprising:
-
one or more namespace domains; and a physical domain interconnect medium for connecting between the namespace domains, wherein each namespace domains includes; one or more messaging appliances configured for receiving and routing messages, an interconnect utilizing channel-based messaging that routes messages over a first messaging layer based on one or more channels mapped to subscription topics, each of the one or more channels assigned to a communication pathway of a second messaging layer; and a provisioning and management system linked via the interconnect to the one or more messaging appliances and configured to exchange administrative messages with each of the one or more messaging appliances, wherein each of the one or more messaging appliances is further configured to execute the routing of messages by dynamically selecting a message transmission protocol and a message routing path.
-
-
39. An enterprise system with a publish/subscribe middleware architecture, comprising:
-
a market data delivery infrastructure having one or more messaging appliances for receiving and routing market data messages; a market order routing infrastructure having one or more messaging appliances to receive and route transaction order messages; and an intermediate infrastructure in communication link with the market data delivery and market order routing infrastructures, respectively, wherein the intermediary infrastructure includes; one or more messaging appliances configured for receiving and routing the market data and transaction order messages, an interconnect utilizing channel-based messaging that routes messages over a first messaging layer based on one or more channels mapped to subscription topics, each of the one or more channels assigned to a communication pathway of a second messaging layer; and a provisioning and management system linked via the interconnect to the one or more messaging appliances and configured for exchanging administrative messages with each of the one or more messaging appliances, including the messaging appliances in the market data delivery and market order routing infrastructures, wherein each of the messaging appliances is further configured to execute the routing of messages it receives by dynamically selecting a message transmission protocol and a message routing path. - View Dependent Claims (40, 41, 42, 43)
-
Specification