Architecture
Hoggar starts as a modular monolith: a single Spring Boot backend with clear module boundaries, so that selected components can become independent services later — only if justified.
Planned No application code exists yet. This section describes the selected target architecture.
Technology choices
| Area | Choice |
|---|---|
| Backend | Java + Spring Boot (Web, Security, Data JPA, Validation), Maven |
| API | REST + OpenAPI |
| Database | PostgreSQL + PostGIS, schema versioned with Flyway |
| Frontend (Phase 1) | Angular + TypeScript, responsive PWA |
| Mobile (Phase 2) | React Native + TypeScript, potentially Expo |
Intentionally deferred
Microservices, Kafka, Kubernetes and Artifactory/Nexus are Deferred until a concrete requirement justifies them.
In this section
- Architecture overview — the target architecture diagram.
- Decision Records (ADRs) — why each decision was made.