Architecture Decision Records
Important architectural decisions are documented as ADRs. Each ADR explains the context, the decision, the alternatives considered, the consequences, and its status.
Before changing an established decision, read the existing ADR and propose a new or superseding ADR — never silently replace a decision.
Initial ADR candidates
These decisions are already selected in the project context. Their ADRs are not yet written.
| ADR | Decision | ADR status |
|---|---|---|
| ADR-001 | Spring Boot as primary backend | Not yet written |
| ADR-002 | Angular + PWA for Phase 1 | Not yet written |
| ADR-003 | React Native for Phase 2 | Not yet written |
| ADR-004 | PostgreSQL + PostGIS | Not yet written |
| ADR-005 | Modular Monolith initially | Not yet written |
| ADR-006 | GitLab Issues/Boards instead of Jira initially | Not yet written |
| ADR-007 | Docs-as-Code + Docusaurus | Not yet written |
| ADR-008 | GitLab Registry before Artifactory/Nexus | Not yet written |
| ADR-009 | No Kafka initially | Not yet written |
| ADR-010 | No Kubernetes initially | Not yet written |
New ADRs start from the ADR template.