Architecture review

A system review with boundaries, data flow, failure modes, and an explicit verdict.

Use this templateDocs template
Architecture reviewA system review with boundaries, data flow, failure modes, and an explicit verdict.

Architecture review — <system>

Author: <name> · Reviewers: <names> · Decision by: <date>

A transparent technical system showing connected architectural layers

Context and constraints

  • <Load, latency, compliance, offline, or ownership constraint>
  • Writes must survive a regional service restart without client data loss.

Proposed boundaries

~mermaid flowchart LR Client --> API API --> Service Service --> Store[(Durable store)] Service --> Queue[(Event stream)] ~

Critical flows

FlowConsistencyFailure response
<Write path><strong/eventual><retry / reject / compensate>

Failure modes

  • Store unavailable: <bounded behavior and recovery>
  • Duplicate delivery: <idempotency boundary>
  • Stale client: <version contract>

Verdict

Important

Approve / Revise / Reject — <why, conditions, and owner>.