MSB Frankfurt Architecture Review

Brief Project Overview (brief as it should be known)

MSB is the infrastructure to support ONAP microservice communication. MSB consists of these sub-components:

• Registry Service information storage, MSB uses Consul as the service registry.
• MSB Discovery Provides REST APIs for service discovery and registration.
• API Gateway Provide service request routing, load balancing and service governance. It can be deployed as external Gateway or Internal Gateway.
• MSB SDK A Java SDK for point to point communication.

New component capabilities for Frankfurt, i.e. the functional enhancements.

• N/A

New or modified interfaces

• N/A

If they are modified, are the backwards compatible?

Yes

Interface naming (point to an example)

• POST /api/microservices/v1/services ( Microservice Bus API Documentation#RegisterservicetotheMicroserviceBus)
• DELETE /api/microservices/v1/services/{serviceName}/version/{version}/nodes/{ip}/{port} (Microservice Bus API Documentation#UnregisterservicefromtheMicroserviceBus )
• GET /api/microservices/v1/services/{serviceName}/version/{version} (Microservice Bus API Documentation#QueryservicefromtheMicroserviceBus)

Reference to the interfaces.

Detailed introduction of APIs can be found here: Microservice Bus API Documentation

What are the system limits?

N/A

Involved use cases, architectural capabilities or functional requirements.

• CCVPN
• vFW/vDNS
• vCPE

• any existing use cases and new use cases in the Frankfurt release.

Listing of new or impacted models used by the project (for information only).

N/A