Distributed computing system architecture

• US 7,444,433 B2
• Filed: 12/13/2006
• Issued: 10/28/2008
• 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 L., Mullins, Chalon G., Richards, Adam J., Levy, David, Sherr, David
• Primary Examiner(s): Cardone; Jason
• Assistant Examiner(s): HOSSAIN, TANIM M
• Application Number:
  US11/638,080
• Publication Number:
  US 20070094416A1
• Time in Patent Office: 685 Days
• Field of Search: 709/201, 709/214, 709/223, 709/253, 719/318
• 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, which comprises:

a bus which includes a channel manager component that provides for at least three different types of channels, the at least three different types of channels including a service channel, an event channel and a stream channel, which provide for communication between a plurality of different service requestors and a plurality of different service providers, and includes a service discovery component that identifies a plurality of different types of interfaces for the plurality of different service providers, wherein the different types of channels correspond to the plurality of different types of interfaces;

a service requestor container operatively coupled to said bus, said service requestor container containing a service requestor application;

a service provider container operatively coupled to said bus, said service provider container containing a service provider application;

wherein the service provider container includes an interaction broker component, said interaction broker providing an interface between said bus and said service provider application;

a virtual data store operatively coupled to said service requestor container and to said service provider container, wherein said virtual data store includes a posting service component operatively coupled to said service provider container;

a read/write data store operatively coupled to said posting service;

an inquiry service component operatively coupled to said service requestor container;

a read-only data store operatively coupled to said inquiry service component; and

,

a replication component operatively coupled to said read-only data store and said read/write data store.

2. The computing system as claimed in claim 1, wherein said service provider container includes a component for advertising the service provided by said service provider application to said service discovery component.

3. The computing system as claimed in claim 2, wherein said service requestor container includes a component for finding a service advertised to said service discovery component.

4. The computing system as claimed in claim 1, including a plurality of service provider containers operatively coupled to said bus, each of said service provider containers containing a service provider application.

5. The computing system as claimed in claim 4, wherein a first of said service provider containers is a publisher container and a second of said service provider containers is a subscriber container.

6. The computing system as claimed in claim 5, wherein:

said publisher container includes a component for advertising publication of an event.

7. The computing system as claimed in claim 5, wherein:

said subscriber container includes a component for subscribing to publication of an event.

8. The computing system as claimed in claim 1, wherein said channel manager component is adapted to create a channel in response to receipt of an open channel message from a first container wherein each of said channels is identified by a logical channel name.

9. The computing system as claimed in claim 8, wherein said logical channel name is a handle dynamically created by said channel manager component.

10. The computing system as claimed in claim 8, wherein said channel manager component is adapted to create a tank, and said logical name is a name of said tank.

11. The computing system as claimed in claim 8, wherein said channel is a service channel.

12. The computing system as claimed in claim 8, wherein said channel is an event channel.

13. The computing system as claimed in claim 8, wherein said channel is an unmapped stream.

14. The computing system as claimed in claim 8, wherein said channel is a mapped stream.

15. The computing system as claimed in claim 14, wherein said channel manager component is adapted to create a tank associated with said mapped stream.

16. The computing system as claimed in claim 1, further comprising a systems management component linked to the bus.

17. The computing system as claimed in claim 1, further comprising a security component linked to the bus.

18. The computing system as claimed in claim 1, wherein the interaction broker component comprises a request broker that invokes an operation by a business service based upon a service request.

19. The computing system as claimed in claim 1, wherein the interaction broker component comprises an event handler, which performs an event-operation mapping to invoke a business service based upon an event.

20. The computing system as claimed in claim 1, wherein the interaction broker component comprises a stream handler, which performs a data-type operation mapping to invoke a business service based upon a stream.