This is a collaboration space to define a reference architecture to carry forward in OSDU.
The principles of the data ecosystem help us make architectural and technical choices that are consistent with our values, over time and across geography.
These are the significant use cases that drive the architecture definition.
This represents the functional capabilities of the system, as observed by the end users.
Non-functional requirements of a system often have a larger impact on architecture than functional requirements.
These are the architectural decisions that are deemed important to produce a coherent system. They are derived from principles, tenets, and requirements but are more prescriptive.
The data ecosystem architectural style is Microservices. This section describes our opinion on what a Microservices architecture is.
This view breaks down the architecture into it's service components. Because we adhere to domain-driven design, the conceptual architecture mirrors the functional architecture.
This positions the architecture in context of the other systems and workflows that interact with the data ecosystem.
This is a view of the deployment architecture to address single customer, multi-customer and enterprise customer concerns.
Some of the security views are listed here.
Some of the operations views are listed here.
The collection of public facing APIs and the principles behind building them