-
Notifications
You must be signed in to change notification settings - Fork 0
ADR Index
Tiana_ edited this page Jun 2, 2026
·
2 revisions
Each ADR captures a significant architectural decision with its context, decision and consequences. Format: Michael Nygard's template. All ADRs are immutable once accepted - superseded ADRs are linked, not overwritten.
| ID | Title | Status | Decided |
|---|---|---|---|
| ADR-0001 | Modular monolith with extraction roadmap | Accepted | 2026-04-25 |
| ADR-0002 | License: BSL 1.1 with 4-year change date | Accepted | 2026-04-25 |
| ADR-0003 | Outbox pattern over direct Kafka publish | Accepted | 2026-04-25 |
| ADR-0004 | Hibernate JPA over R2DBC for v0.1 | Accepted | 2026-04-25 |
| ADR-0005 | Keycloak as identity provider | Accepted | 2026-04-25 |
| ADR-0006 | Redpanda default broker (Kafka-compatible) | Accepted | 2026-04-25 |
| ADR-0007 | Double-entry invariant enforced at DB level | Accepted (amended by ADR-0012) | 2026-04-25 |
| ADR-0008 | JSON DSL for decision engine rules | Accepted | 2026-04-25 |
| ADR-0009 | BSL chosen over AGPL: rationale | Accepted | 2026-04-25 |
| ADR-0010 | Prefixed ULID identifiers at the API edge | Accepted | 2026-05-30 |
| ADR-0011 | Account balance as an incremental row, not a per-post materialized view | Accepted | 2026-05-30 |
| ADR-0012 | Single-currency transactions, FX via linked legs | Accepted | 2026-06-01 |
- Proposed → discussion in PR
- Accepted → merged, immutable
- Deprecated → replaced by another ADR (link forward)
- Superseded → see linked successor
See ADR-Process for the full workflow.
- Overview
- Services
- Data Model
- Domain Model
- Event Flow
- Security
- Observability
- Resilience
- SLA / SLI / SLO