Architecture Decision Records (ADRs): Documenting the Why

Why did we choose Cosmos DB over SQL? Why did we use gRPC here?

Six months from now, nobody will remember. That’s why you need ADRs. An ADR is a short markdown file stored in the repo that captures an architectural decision.

Structure

  • Title: “Use Cosmos DB for Session Store”
  • Status: Accepted / Deprecated
  • Context: We need high write throughput…
  • Decision: We will use Cosmos…
  • Consequences: Cost will be higher, but latency lower.

Treat architecture decisions like code. Review them in PRs. Commit them to history.


Discover more from C4: Container, Code, Cloud & Context

Subscribe to get the latest posts sent to your email.

Leave a comment

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.