Cloud-Native Architecture

Definition: Architecture Decision Record from where you should specialise the ADR SBBs regarding the Cloud-Native Architecture

Source: ISO/IEC/IEEE 42010:2022

Source reference: https://www.iso.org/standard/74393.html

Additional information: Cloud-native architecture is designed specifically for cloud environments, leveraging cloud computing capabilities and services. It emphasizes scalability, fault tolerance, and the use of containerization and orchestration tools like Docker and Kubernetes. Cloud-native applications are typically built using microservices and take advantage of cloud services such as storage, databases, and messaging queues.

Example: Title: Cloud-Native Architecture Decision Record (ADR)

LOST view: Digital Solution Architecture Decisions Catalogue view

Identifier: http://data.europa.eu/dr8/egovera/Cloud-NativeArchitectureGoal

EIRA traceability: eira:DigitalSolutionArchitectureDecisionGoal

ABB name: egovera:Cloud-NativeArchitectureGoal

EIRA concept: eira:ArchitectureBuildingBlock

Last modification: 2023-08-20

dct:identifier: http://data.europa.eu/dr8/egovera/Cloud-NativeArchitectureGoal

dct:title: Architecture Decision Record about Cloud-Native Architecture

eira:adr_context: The context explains why we need to make a decision. It also describes the alternatives along with the pros and cons.

eira:adr_decision: The decision describes the justification for why the particular solution was accepted. It has more emphasis on the why rather than the how.

eira:adr_status: [Proposed (under review)|Accepted (approved and ready for implementation)|Superseded (superseded by another decision)]

eira:adr_consecuences: The consequences section contains information about the overall impact of an architectural decision. Every decision has trade-offs. That’s why it’s crucial to include the analysis to provide a clear picture.