9. Architecture Decisions
All architectural decisions for PSSaaS are documented as Architecture Decision Records (ADRs) in a dedicated section. Each ADR captures the context, decision, and consequences of a significant architectural choice.
ADR Index
| ADR | Title | Status |
|---|---|---|
| ADR-001 | Backend Technology — .NET 8 / C# | Accepted |
| ADR-002 | Frontend Technology — React + TypeScript | Accepted |
| ADR-003 | Cloud Strategy — Azure-Preferred, Vendor-Agnostic | Accepted |
| ADR-004 | Architecture Style — Modular Monolith First | Accepted |
| ADR-005 | Database Strategy — SQL MI with Database-Per-Tenant | Accepted |
| ADR-006 | Schema Migration — Preserve Initially, Modernize Incrementally | Accepted |
| ADR-007 | Target Audience — New Customers First | Accepted |
| ADR-008 | UX Strategy — Modern Default + Power Opt-In | Accepted |
| ADR-009 | Documentation Platform — Docusaurus | Accepted |
| ADR-010 | Documentation Framework — Arc42 + ADRs + Specs Before Code | Accepted |
| ADR-011 | Ecosystem Product Boundaries | Accepted |
| ADR-012 | Business Operations Platform — Odoo | Accepted |
| ADR-013 | Identity Strategy | Proposed |
| ADR-014 | Backend Language Divergence Accepted | Accepted |
| ADR-015 | Desktop App Coexistence | Accepted |
| ADR-016 | Local Reverse Proxy and Docker Compose Profiles | Accepted |
| ADR-017 | Ecosystem Hostname Convention | Accepted |
| ADR-018 | Local SQL Server Container for Development | Accepted |
| ADR-019 | PSX-to-SaaS BestEx Integration | Proposed |
| ADR-020 | Shared Kubernetes Cluster with PSX | Proposed |
| ADR-021 | PowerFill Port Strategy | Proposed |
| ADR-022 | PowerFill Allocation Algorithm | Proposed |
| ADR-023 | PowerFill Constraint Model | Proposed |
| ADR-024 | PowerFill Async Run Pattern | Proposed |
| ADR-025 | PowerFill Report API Pattern (Phase 7) | Proposed |
| ADR-026 | Frontend Framework + Build Pipeline (Phase 8 W2) | Proposed |
| ADR-027 | Superset Embedding Strategy (Phase 8.5) | Accepted |
| ADR-028 | Phase 9 Parallel Validation Harness Design | Proposed |
| ADR-029 | PSSaaS Tenant Identity Strategy (Phase 8.5 W4 — A68 long-term decoupling code shape) | Accepted |
Process
- ADRs are numbered sequentially and never renumbered
- Superseded ADRs are marked as such and link to their replacement
- ADRs follow a consistent format: Context → Decision → Consequences
- All ADRs are reviewed as part of the documentation process