Asynchronous channel based bus architecture enabling decoupled services

• US 10,678,735 B2
• Filed: 06/27/2017
• Issued: 06/09/2020
• Est. Priority Date: 06/27/2017
• Status: Active Grant

• Current Assignee: Vmware LLC (Broadcom, Inc.)
• Original Assignee: VMware, Inc. (Broadcom, Inc.)
• Inventors: Shanley, Dave
• Primary Examiner(s): Tsai, Henry
• Assistant Examiner(s): Bartels, Christopher A
• Application Number:
  US15/635,043
• Publication Number:
  US 20180373661A1
• Time in Patent Office: 1,078 Days
• Field of Search: None
• CPC Class Codes: G06F 13/4027 using bus bridges G06F13/4022 takes precedence
• CPC Class Codes: G06F 9/544 Buffers; Shared memory; Pipes

Abstract

In an asynchronous channel based bus architecture enabling decoupled services, there is an asynchronous channel based bus having at least one channel. A first service is coupled to the asynchronous channel based bus, the first service passes messages to and receives messages on the at least one channel. A second service is also coupled to the asynchronous channel based bus, the second service also passes messages to and receive messages on the at least one channel.

Claims

1. A system comprising:

an asynchronous channel based bus having at least one channel;

a first service hooked to the at least one channel without being registered with a second service, the first service to pass messages to and receive messages on the at least one channel; and

the second service hooked to the at least one channel without being registered with the first service, the second service to pass messages to and receive messages on the at least one channel,

wherein the at least one channel is configured as a Galactic channel, and

wherein messages received from the at least one Galactic channel are converted from a channel message format used by the at least one Galactic channel to a common message format.

2. The system of claim 1, wherein the asynchronous channel based bus allows a dynamic creation of a plurality of channels.

3. The system of claim 2, wherein the asynchronous channel based bus allows a dynamic destruction of any of the plurality of channels.

4. The system of claim 2, wherein the asynchronous channel based bus allows any actor to subscribe to any of a plurality of channels on the bus.

5. The system of claim 1, wherein the first service is not coupled with the second service.

6. The system of claim 1, wherein a dependency between the first service and the second service is a single entity.

7. The system of claim 1, wherein the asynchronous channel based bus allows each message to be performed in small asynchronous units of work, such that a call stack for each of the first service and the second service is cleared and each of the first service and the second service can process or send another message.

8. The system of claim 1, wherein the first service and the second service do not have to change API signatures before they hook into the at least one channel.

9. The system of claim 1, wherein each message provided by the first service on the bus is provided asynchronously and each message provided by the second service on the bus is provided asynchronously, such that no call chaining exists between the first service and the second service.

10. The system of claim 1, further comprising:

an nth service coupled to the asynchronous channel based bus,

the nth service to pass messages to and receive messages on the at least one channel, and

the nth service composed into a module with the first service to form a first microservice.

11. The system of claim 10, wherein each message, on the bus, provided by the first service, the second service, and the nth service is provided asynchronously such that no call chaining exists between any of the first service, the second service and the nth service.

12. A computer-implemented method for using an asynchronous channel based bus architecture to enable decoupled services, the computer-implemented method comprising:

providing an asynchronous channel based bus having at least one channel;

hooking a first service into the at least one channel without registering the first service with a second service, the first service to pass messages to and receive messages on the at least one channel; and

hooking the second service into the at least one channel without registering the second service with the first service, the second service to pass messages to and receive messages on the at least one channel,

wherein the at least one channel is configured as a Galactic channel, and

wherein messages received from the at least one Galactic channel are converted from a channel message format used by the at least one Galactic channel to a common message format.

13. The computer-implemented method of claim 12, wherein

prior to hooking into the at least one channel, the first service and the second service do not have to change respective API signatures.

14. The computer-implemented method of claim 12, further comprising:

allowing a dynamic creation of a plurality of channels within the asynchronous channel based bus; and

allowing a subsequent destruction of one or more of the plurality of channels within the asynchronous channel based bus.

15. The computer-implemented method of claim 12, further comprising allowing the first service and the second service to publish to, and receive from, any of the plurality of channels of the asynchronous channel based bus.

16. The computer-implemented method of claim 12, further comprising:

providing each message from the first service on the bus asynchronously; and

providing each message from the second service on the bus asynchronously, such that no call chaining exists between the first service and the second service.

17. A computer-implemented method for using an asynchronous channel based bus architecture to enable decoupled services, the computer-implemented method comprising:

providing an asynchronous channel based bus having at least one Galactic channel;

hooking a first service into the at least one Galactic channel on the asynchronous channel based bus, the first service to pass messages to and receive messages on the at least one Galactic channel;

hooking at least a second service into the at least one Galactic channel on the asynchronous channel based bus, the second service to pass messages to and receive messages on the at least one Galactic channel;

communicatively coupling a bridge to the at least one Galactic channel of the asynchronous channel based bus;

distributing, via the bridge, at least one message on the at least one Galactic channel to a different Galactic channel;

simultaneously distributing, via the bridge, at least one message on the at least one Galactic channel to a plurality of message brokers; and

redistributing, by the plurality of message brokers, the at least one message to a plurality of bridges, each of the plurality of bridges coupled to a different asynchronous channel based bus, each different asynchronous channel based bus having at least one Galactic channel thereon.

18. The computer-implemented method of claim 17, further comprising:

converting, via a message translator coupled with the bridge, every message received from the at least one galactic channel from a channel message format used by the at least one galactic channel to a common message format.