Distributed computing system architecture

• US 8,886,841 B2
• Filed: 04/19/2012
• Issued: 11/11/2014
• Est. Priority Date: 02/22/2001
• Status: Expired due to Term

• Current Assignee: Charles Schwab & Company Incorporated (Charles Schwab Corporation)
• Original Assignee: Charles Schwab & Company Incorporated (Charles Schwab Corporation)
• Inventors: Goldstein, Neal, Richards, Adam, Sherr, David, Levy, David, Mullins, Chalon
• Primary Examiner(s): COULTER, KENNETH R
• Application Number:
  US13/451,421
• Publication Number:
  US 20120265915A1
• Time in Patent Office: 936 Days
• Field of Search: 709/253, 709/223, 709/238
• US Class Current: 709/253
• CPC Class Codes: G06F 2209/547 Messaging middleware
• CPC Class Codes: G06F 9/546 Message passing systems or structures, e.g. queues
• CPC Class Codes: H04L 12/1859 adapted to provide push services, e.g. data channels
• CPC Class Codes: H04N 21/266 Channel or content management, e.g. generation and management of keys and entitlement messages in a conditional access system, merging a VOD unicast channel into a multicast channel
• CPC Class Codes: H04N 21/2668 Creating a channel for a dedicated end-user group, e.g. insertion of targeted commercials based on end-user profiles information retrieval from the Internet by querying with filtering and personalisation G06F16/9535; arrangements for replacing or switching information during the broadcast H04H20/10; push services over packet-switching network H04L12/1859; adaptation of message content in packet-switching networks H04L51/063

Abstract

A computing system architecture is based upon a peer-to-peer, asynchronous model. The architecture specifies a set of infrastructure facilities that comprise an inter-prise operating system. The inter-prise operating system provides all the facilities that make application coding as easy in the peer-to-peer asynchronous model as it is in a hierarchical, synchronous model. Services, which reside in containers, are linked asynchronously by an inter-prise bus and use data from a virtual data store.

Claims

1. A computing system, comprising:

a bus including;

a channel manager component that provides for at least three types of channels for communication between a plurality of service requestors and a plurality of service providers, wherein the channel manager component is adapted to create a channel in response to receipt of an open channel message, and the at least three types of channels include a service channel for communication of a request for a service, an event channel for communication of events raised or handled by the service, and a stream channel for communication of data read or written by the service; and

a service discovery component that identifies a plurality of interfaces corresponding to the plurality of service providers;

a service requestor container coupled to the bus, the service requestor container containing a service requestor application; and

a service provider container coupled to the bus, the service provider container containing a service provider application.

2. The computing system of claim 1, wherein the channel manager component is adapted to create a service channel in response to receipt of an open channel message from the service provider container for the service provider application, and to return a handle to the service provider container, the handle being a logical name of the service channel created.

3. The computing system of claim 2, wherein the service provider container is adapted to send the handle to the service discovery component to advertise the service provider application.

4. The computing system of claim 3, wherein the service discovery component is adapted to send the handle to the service requestor container in response to receipt of a find service message from the service requestor container.

5. The computing system of claim 4, wherein the service requestor container is adapted to invoke the service provider application for the service requestor application by sending a request to the service provider container.

6. The computing system of claim 5, wherein the service requestor application is a subscriber application, and the service provider application is a publisher application.

7. The computing system of claim 6, wherein the channel manager component is adapted to create an event channel in response to receipt of an open event channel message from the service provider container for the publisher application, and to return a handle to the service provider container, the handle being a logical name of the event channel created.

8. The computing system of claim 7, wherein the service provider container is adapted to send the handle to the service discovery component to advertise the publisher application.

9. The computing system of claim 8, wherein the service discovery component is adapted to send the handle to the service requestor container in response to receipt of a find channel message from the service requestor container.

10. The computing system of claim 9, wherein the service requestor container is adapted to send a subscriber open event channel message to the channel manager component to subscribe the subscriber application to the event channel created.

11. The computing system of claim 1, wherein the computing system further includes a source and a sink coupled to the bus.

12. The computing system of claim 11, wherein the stream channel is a mapped stream channel, and the channel manager component is adapted to open a tank to store data written by the source in response to receipt of an open channel message from the source.

13. The computing system of claim 12, wherein the channel manager component is adapted to read the data stored in the tank in response to receipt of an open channel message from the sink.

14. The computing system of claim 13, wherein the stream channel is an unmapped stream channel, and channel manager component is adapted to create a stream channel in response to receipt of an open channel message from the source, and to return a handle to the source, the handle being a logical name of the stream channel created.

15. The computing system of claim 14, wherein the source is adapted to send the handle to the sink to enable the sink to open the stream channel created.

16. The computing system of claim 1, wherein when the service goes out of service, the service provider container is adapted to send a de-advertise message to the service discovery component and a close channel message to the channel manager component.

17. The computing system of claim 1, wherein the bus is adapted to transmit messages that include system-defined contexts, the system-defined contexts including security contexts, audit contexts , and monitoring contexts.