A real concern is the potential that the CPS will make managing coupling between ONAP components difficult.
Decision
Details
In a micro-service architecture strives to control coupling. The deployment of micro-services enforces good behavior, only published interfaces are available. This is not new. Encapsulation and data hiding have been around as long as software.So too have mechanisms been put in place to soften this encapsulation: the C++ friend declaration; Java package protected. There are reasons for both approaches and as always there is a balance. The two approaches are not mutually exclusive.
By making data available to all, this control is potentially eroded. Some interesting reading on the subject:
- https://microservices.io/patterns/data/shared-database.html
- https://microservices.io/patterns/data/database-per-service.html
There are several aspects to this item. For the purposes of this conversation, a couple of very limited definitions:
- A Common Information Model is the ability to understand data. It is available to all.
- A Data Lake is the ability to access data. It is available to all.
- Access Control is a mechanism to grant or deny access to models or data