STATUS: DraftPTL approved, waiting for architecure approval
MSB (Micro Service Bus):
1 High Level Component Definition and Architectural Relationships
...
| Drawio | ||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
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:
...
OOM connects to MSB to register and update service information when it instantiates service endpoints. Question: How do we differentiate between when to use MSB vs When to use DMaaP?
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.
2. API definitions
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. |
...
3. Component Description:
A more detailed figure and Add link to read-the-docs description of the component.<< For later inclusion >>
4. known system limitations
...
6. System Deployment Architecture
This needs to be updated, what should be here?
MSB consists of 5 containers:
...
FFS
7. New Capabilities in this Release
...