... | @@ -7,19 +7,19 @@ The principles of the data ecosystem help us make architectural and technical ch |
... | @@ -7,19 +7,19 @@ The principles of the data ecosystem help us make architectural and technical ch |
|
These are the significant use cases that drive the architecture definition.
|
|
These are the significant use cases that drive the architecture definition.
|
|
|
|
|
|
## [Functional Architecture](/OSDU-\(C\)/Reference-Architecture/Functional-Architecture)
|
|
## [Functional Architecture](/OSDU-\(C\)/Reference-Architecture/Functional-Architecture)
|
|
This represents the functional capabilities of the system as observed by the end users.
|
|
This represents the functional capabilities of the system, as observed by the end users.
|
|
|
|
|
|
## [Non Functional Requirements](/OSDU-\(C\)/Reference-Architecture/Qualities)
|
|
## [Non Functional Requirements](/OSDU-\(C\)/Reference-Architecture/Qualities)
|
|
Non-functional requirements of a system often have a larger impact on architecture than functional requirements.
|
|
Non-functional requirements of a system often have a larger impact on architecture than functional requirements.
|
|
|
|
|
|
## [Architectural Decisions](/OSDU-\(C\)/Reference-Architecture/Decisions)
|
|
## [Architectural Decisions](/OSDU-\(C\)/Reference-Architecture/Decisions)
|
|
These are the architectural decisions that are deemed important to produce a coherent system. They are derived from principles, tenets, requirements but are more prescriptive.
|
|
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.
|
|
|
|
|
|
## [Architectural Style](/OSDU-\(C\)/Reference-Architecture/Style)
|
|
## [Architectural Style](/OSDU-\(C\)/Reference-Architecture/Style)
|
|
The data ecosystem architectural style is Microservices. This section describes our opinion on what a Microservices architecture is.
|
|
The data ecosystem architectural style is Microservices. This section describes our opinion on what a Microservices architecture is.
|
|
|
|
|
|
## [Conceptual Architecture](/OSDU-\(C\)/Reference-Architecture/Conceptual-Architecture)
|
|
## [Conceptual Architecture](/OSDU-\(C\)/Reference-Architecture/Conceptual-Architecture)
|
|
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 view breaks down the architecture into it's service components. Because we adhere to domain-driven design, the conceptual architecture mirrors the functional architecture.
|
|
|
|
|
|
## [System Context](/OSDU-\(C\)/Reference-Architecture/Context)
|
|
## [System Context](/OSDU-\(C\)/Reference-Architecture/Context)
|
|
This positions the architecture in context of the other systems and workflows that interact with the data ecosystem.
|
|
This positions the architecture in context of the other systems and workflows that interact with the data ecosystem.
|
... | | ... | |