Version: v3.0 | Date: 2026-07-10 Design Philosophy: Pragmatic service decomposition. Modular monolith inside core-service. Extract only when necessary.
This document has been split into 3 focused docs for easier navigation.
| Document | Content |
|---|---|
| System Architecture Overview | Philosophy, service decomposition, C4 model, data architecture, API gateway, event-driven communication, shared kernel, security, observability, deployment, ADRs, boundary enforcement, rationale |
| Frontend Architecture | Feature-based module architecture, package ecosystem, component boundaries, server-driven routing, state management, design token architecture, i18n architecture, boundary enforcement |
| Backend Architecture | Core-service modular monolith, bounded contexts as NestJS modules, event-driven communication, module boundary enforcement |
| # | Section | Current Location |
|---|---|---|
| 1 | Architecture Philosophy | System Overview |
| 2 | Service Decomposition — 5 Services | System Overview |
| 3 | Core-Service: The Modular Monolith | Backend Architecture |
| 4 | Bounded Contexts as NestJS Modules | Backend Architecture |
| 5 | C4 Model — System Landscape | System Overview |
| 6 | Data Architecture | System Overview |
| 7 | API Gateway Design | System Overview |
| 8 | Event-Driven Communication | System Overview & Backend |
| 9 | Shared Kernel & Package Strategy | System Overview |
| 10 | Frontend Architecture | Frontend Architecture |
| 11 | Security Architecture | System Overview |
| 12 | Observability & Operations | System Overview |
| 13 | Deployment Architecture | System Overview |
| 14 | Architecture Decision Records | System Overview |
| 15 | Module Boundary Enforcement | System Overview & Backend |
| 16 | Why This Design Works | System Overview |