Architecture Decision Records
Architecture Decision Records document significant architectural decisions made for StandardOps.
ADRs capture the context, alternatives considered, decision, consequences, and reasoning behind important technical and architectural choices.
They provide a durable record of why the platform architecture evolved in a particular direction.
ADRs
| ADR | Decision | Status |
|---|---|---|
| ADR-0001 | Adopt Microservices Based on Business Capabilities | Accepted |
| ADR-0002 | Adopt Multi-Tenant SaaS Architecture | Accepted |
| ADR-0003 | Define Service Data Ownership and Tenant Data Isolation | Accepted |
| ADR-0004 | Adopt Event-Driven Integration | Accepted |
| ADR-0005 | Define Synchronous Service Communication | Accepted |
| ADR-0006 | Define Authentication, Organization Membership, and Authorization | Accepted |
| ADR-0007 | Define API Gateway and External API Architecture | Accepted |
ADR Lifecycle
ADRs may have one of the following statuses:
- Proposed
- Accepted
- Rejected
- Deprecated
- Superseded
Accepted ADRs should not normally be rewritten to reflect later decisions.
When an architectural decision changes, a new ADR should document the new decision and reference the ADR it supersedes.