...
- How does this project fit into the rest of the ONAP Architecture?
DMaaP has four components:
- Message Router (MR) -Message Router is a reliable, high-volume pub/sub messaging service with a RESTful HTTP API. It is intended to be deployed by Platform Service providers so that it is available to Platform clients as a web service. The service is initially built over Apache Kafka, with some important additional features which focus on integration with other Platform services such as provisioning and authorization.
- Data Router (DR) - The Data Routing System project is intended to provide a common framework by which data producers can make data available to data consumers and a way for potential consumers to find feeds with the data they require. The interface to DR is exposed as a RESTful web service known as the DR Publishing and Delivery API
- Data Movement Director (DMD) - A client to DMaaP platform to publish & subscribe data.
- Data Bus Controller - Provisioning API of the Data Movement Platform.
- Message Router (MR) -
Message Router:
In DMaaP Message Router, Restful web service is exposed to client to perform any needed action with Kafka. After getting the request it calls the Message router service layer which is created using AJSC. AJSC finally calls Kafka services and response is sent back.
Data Router:
- How does this align with external standards/specifications?
- APIs/Interfaces
- Information/data models
- Are there dependencies with other open source projects?
AJSC, DME, AAF, Apache Kafka and Zookeeper.
...