STATUS: PTL approved, waiting for architecure approval
The Microservice Bus function provides service registration, discovery and communication services for microservices as well as a gateway for internal & External communication for the services:
Register communication services
Discover communication services
Manage communication between microservices
OOM connects to MSB to register and update service information when it instantiates service endpoints.
MSB and DMaaP are complementary. MSB provides the restful API service registration/discovery/routing/API gateway, which addresses the sync/rpc communication pattern in microservice architecture, in contrast, DMaaP provides messages/file transfer, which mainly focused on the async communication pattern in microservices architecture.
MSB provides the following interfaces: (Question, is this one interface with 3 LCMs or one interface with these capabilities)
| Interface Name | Interface Definition | Interface Capabilities |
|---|---|---|
| MSBE-1 | Registration and Discovery interface | The registration and discovery interface provides the following capabilities:
|
| MSBE-2 | Service Request Interfaces | Provides the capability to deliver and recieve a service request and subsequent communication. |
| MSBE-3 | MSB Admin Interface | Provides the ability to administer policy and routing for the service requests. |
Note: xxxI interface is a Component internal interface. xxxxE interface is a component external interface
The current API documents can be found at:
MSB consumes the following Interfaces:
| Interface Name | Purpose Reason For Use |
|---|---|
| N/A | N/A |
Add link to read-the-docs description of the component
MSB API gateway has been tested in this scenario:
The test result is 50000 request per second.
MSB uses the following models:
FFS
This release, MSB adds the following Capabilities: