Abstract: Embodiments manage a lifecycle of distributed data objects from at least a first data fabric node. Embodiments receive a request from a publisher to anchor a scope. Embodiments anchor the scope to an anchor in the first data fabric node to generate an anchored scope, where the anchor includes a previously published first object and a corresponding first lifecycle and anchoring the scope includes registering interest in the first lifecycle of the anchor. Embodiments publish, by the first data fabric node, scope metadata corresponding to the anchored scope. Embodiments then receive a request from the publisher to publish a second object into the anchored scope to define an anchored object, the anchored object including the first lifecycle.

Abstract: Embodiments operate a data fabric node architecture that includes one or more data fabric nodes. Embodiments receive a session initiation from a client application and publish corresponding session metadata to the data fabric. Embodiments receive from the client application a query and perform syntactic analysis and publish a result of the analysis to the data fabric as a query metadata. Embodiments then anchor the query metadata in the data fabric to the session metadata.

Abstract: Embodiments perform gateway routing by receiving an application programming interface (“API”) request for an API from a client for a resource from a first endpoint, wherein a plurality of endpoints each include an instance of the API and each endpoint is associated with a unique identifier. The first API request includes a path that specifies a single unique identifier. Embodiments route the first API request to the first endpoint associated with the single unique identifier.

Abstract: Embodiments manage a lifecycle of distributed data objects from at least a first data fabric node. Embodiments receive a request from a publisher to anchor a scope. Embodiments anchor the scope to an anchor in the first data fabric node to generate an anchored scope, where the anchor includes a previously published first object and a corresponding first lifecycle and anchoring the scope includes registering interest in the first lifecycle of the anchor. Embodiments publish, by the first data fabric node, scope metadata corresponding to the anchored scope. Embodiments then receive a request from the publisher to publish a second object into the anchored scope to define an anchored object, the anchored object including the first lifecycle.

Abstract: Embodiments manage a lifecycle of distributed data objects from at least a first data fabric node. Embodiments receive a request from a publisher to anchor a scope. Embodiments anchor the scope to an anchor in the first data fabric node to generate an anchored scope, where the anchor includes a previously published first object and a corresponding first lifecycle and anchoring the scope includes registering interest in the first lifecycle of the anchor. Embodiments publish, by the first data fabric node, scope metadata corresponding to the anchored scope. Embodiments then receive a request from the publisher to publish a second object into the anchored scope to define an anchored object, the anchored object including the first lifecycle.

Abstract: Embodiments manage a lifecycle of distributed data objects from at least a first data fabric node. Embodiments receive a request from a publisher to anchor a scope. Embodiments anchor the scope to an anchor in the first data fabric node to generate an anchored scope, where the anchor includes a previously published first object and a corresponding first lifecycle and anchoring the scope includes registering interest in the first lifecycle of the anchor. Embodiments publish, by the first data fabric node, scope metadata corresponding to the anchored scope. Embodiments then receive a request from the publisher to publish a second object into the anchored scope to define an anchored object, the anchored object including the first lifecycle.

Abstract: The invention relates to integration of streaming data. The invention provides a means for integrating both high-throughput streaming and static content originating from multiple types and/or instances of data sources into discrete units of data. The invention provides integration of a wide variety of disparate streaming and static data sources as well as deployment of content in multiple protocols, either static or streaming or both. In the preferred embodiment, the invention provides a method and system for the insertion of domain-specific implementations of the JMS (Java Message System) messaging paradigm into a server-based JMS provider infrastructure. A Content Integration Framework provides access to Content Instances. The Content Integration Framework is used by Distribution Adapters that expose content from Content Instances cached in the system using a variety of protocols.

Abstract: The invention provides plug-in framework, enabling embedding of content-based processes to in a messaging paradigm provider service. In the preferred embodiment, the messaging paradigm is JMS and the invention provides a plug-able framework embedded in a JMS Provider. The plug-able server is particularly suited for efficient and secure transmission of real-time, streaming data.

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.

Abstract: The invention provides a system and method whereby an Application may use a standard API to access and deliver financial market data from multiple proprietary Market Data Systems. In the preferred embodiment, a JMS API is used, along with a small set of conventions, that enable an application to access market data from Market Data Systems though a standardized interface using the JMS publish/subscribe paradigm, and wherein said standardized interface relies on a small set of conventions to convey market data semantics via the standard JMS message property construct.

Abstract: In a client server network, the invention provides improved message routing, useful in sending a plurality of subscriber messages from a single Server published message. The invention provides all the benefits of TCP delivery with most of the efficiency of IP multicast delivery. The invention provides for a Controller associated in the Client Server communication, where the Controller effectively routes the Server message to subscribed Clients. The invention provides efficient distribution of streaming data to one or more consumers in a way that enables easy integration in consuming applications. The invention provides means to implement a Java Message Service (JMS) distribution adapter in hardware. The invention further provides for hardware implementation of various wire protocol transforms.

Abstract: The invention provides plug-in framework, enabling embedding of content-based processes to in a messaging paradigm provider service. In the preferred embodiment, the messaging paradigm is JMS and the invention provides a plug-able framework embedded in a JMS Provider. The plug-able server is particularly suited for efficient and secure transmission of real-time, streaming data.

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.

Abstract: The invention relates to integration of streaming data. The invention provides a means for integrating both high-throughput streaming and static content originating from multiple types and/or instances of data sources into discrete units of data. The invention provides integration of a wide variety of disparate streaming and static data sources as well as deployment of content in multiple protocols, either static or streaming or both. In the preferred embodiment, the invention provides a method and system for the insertion of domain-specific implementations of the JMS (Java Message System) messaging paradigm into a server-based JMS provider infrastructure. A Content Integration Framework provides access to Content Instances. The Content Integration Framework is used by Distribution Adapters that expose content from Content Instances cached in the system using a variety of protocols.