Architecture Decision Records (ADRs)

Architecture Decision Records (ADR) are documented architectural decisions, each of which clarifies specific coding rules and guidelines that collectively shape our codebase.

Purpose of ADRs

ADRs serve as a living record of important technical decisions made throughout the project. They help teams understand the rationale behind architectural choices, ensure consistency, and support onboarding of new developers. By documenting the context, decision, and consequences, ADRs make it easier to revisit and adapt decisions as requirements evolve.

Each ADR follows a standardized template to ensure clarity and comparability. The template can be found in ADR-00 Is-Template. New ADRs should be added whenever a significant architectural or coding decision is made, and existing ADRs should be updated if decisions change.

ADRs in the project

• ADR-01 Use-Immutable-Variables
• ADR-02 No-Column-Annotation
• ADR-03 Use-Test-File-Suffix
• ADR-04 Use-Test-Nested-Class
• ADR-05 Use-Test-Method-Prefix
• ADR-06 Use-Test-Data-Attribute
• ADR-07 Reduce-Testing-Of-Mapping
• ADR-08 Define-Dtos-As-Records
• ADR-09 No-Complex-Frontend-Components
• ADR-10 Send-Api-Error-Message
• ADR-11 Use-Directory-Structure
• ADR-12 Use-Comments
• ADR-13 Use-Consistent-Code-Language