Monolithic Architecture

Definition: Architecture Decision Record from where you should specialise the ADR SBBs regarding the Event-Driven Architecture

Source: ISO/IEC/IEEE 42010:2022

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

Additional information: In a monolithic architecture, the entire application is built as a single, self-contained unit. All components of the application are tightly coupled, and any changes or updates require modifying the entire system. This architecture is straightforward to develop and deploy but can become complex and difficult to scale or maintain as the application grows.

Example: Title: Monolithic Architecture Decision Record (ADR)

LOST view: Digital Solution Architecture Decisions Catalogue view

Identifier: http://data.europa.eu/dr8/egovera/MonolithicArchitectureGoal

EIRA traceability: eira:DigitalSolutionArchitectureDecisionGoal

ABB name: egovera:MonolithicArchitectureGoal

EIRA concept: eira:ArchitectureBuildingBlock

Last modification: 2023-07-06

dct:identifier: ADR-20230606091024763

dct:title: Architecture Decision Record about Monolithic 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.