Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 13 Next »

STATUS: PTL approved, waiting for architecure approval

MSB (Micro Service Bus):

1 High Level Component Definition and Architectural Relationships 



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. 

2. API definitions

MSB provides the following interfaces:

Interface NameInterface Definition Interface Capabilities
MSBE-1Registration and Discovery interface The registration and discovery interface provides the following capabilities:
  • Register/Unregister a service
  • Discover a service 
MSBE-2Service Request Interfaces

Provides the capability to deliver and recieve a service request and subsequent communication.

MSBE-3  MSB Admin InterfaceProvides 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 NamePurpose Reason For Use
N/AN/A


3. Component Description:

A more detailed figure and description of the component.

<< For later inclusion >>

4. known system limitations



MSB API gateway has been tested in this scenario:

  • Client(wrk) --> MSB API gateway --> Test service(Tomcat)
  • Test machine (client, msb and test service): 8 cpu Core, 8G memory
  • Network 10000M 

The test result is 50000 request per second.

5. Used Models

MSB uses the following models:

  • -


6. System Deployment Architecture

MSB consists of 5 containers:

  • MSB Consul container
  • MSB Discovery container
  • MSB IAG (Internal API Gateway) container
  • MSB EAG (External API Gateway)  container
  • Kube2MSB container 

7. New Capabilities in this Release

This release, MSB adds the following Capabilities:

  • -

8. References

  1. Microservice Bus API Documentation  


  • No labels