Skip to content

Architecture decision record

Record a technical decision with its context, options, reasons and consequences, for the team to find later.

Fill it in and preview

ADR-0012: Use PostgreSQL for the orders service

Status: Status
Date: 12 March 2027
Decision makers: Platform team lead, orders team lead, security engineer

Context

The orders service stores 20 million rows and needs transactions across tables. The current store has no transaction support and the team has no experience running it.

What matters most

Data consistency
Team experience
Running cost
Ability to scale to 5x in two years

Options considered

1. PostgreSQL, managed. Strong transactions, team knows it, higher cost.
2. A document database. Fast to start, weaker joins and transactions.
3. Stay with the current store. No migration, but the problem remains.

Decision

We will use managed PostgreSQL for the orders service.

Why

It meets the consistency need, the team can support it, and cost is acceptable within the platform budget.

Consequences

Good: simpler code and safer orders. Bad: a three month migration and a yearly hosting cost. We must plan the data move and a rollback.

When to revisit

If volume passes 100 million rows or hosting costs double.

Related

Replaces ADR-0004. Related: ADR-0009.

Templates are a careful starting point, not legal advice. Where the law matters, check what applies where you are.

IT and projects

What this template is for

An architecture decision record: the context, options considered, decision, reasons and consequences, so the team remembers why a technical choice was made.

It is free to fill in online, needs no account, and downloads as a Word document or a PDF. See all IT and projects templates

IT and projects

What you fill in

The form asks for 13 details. The document fills itself in as you type.

  • Record number

    For example: ADR-0012

  • Decision title

    For example: Use PostgreSQL for the orders service

  • Status

  • Date

    For example: 12 March 2027

  • Decision makers

    For example: Platform team lead, orders team lead, security engineer

  • Context

    The problem, the forces and the limits.

    For example: The orders service stores 20 million rows and needs transactions across tables. The current store has no transaction support and the team has no experience running it.

  • What matters most

    One per line, most important first.

    For example: Data consistency Team experience Running cost Ability to scale to 5x in two years

  • Options considered

    Include the options you rejected.

    For example: 1. PostgreSQL, managed. Strong transactions, team knows it, higher cost. 2. A document database. Fast to start, weaker joins and transactions. 3. Stay with the current store. No migration, but the problem remains.

  • Decision

    For example: We will use managed PostgreSQL for the orders service.

  • Why

    For example: It meets the consistency need, the team can support it, and cost is acceptable within the platform budget.

  • Consequences

    Both good and bad.

    For example: Good: simpler code and safer orders. Bad: a three month migration and a yearly hosting cost. We must plan the data move and a rollback.

  • When to revisitoptional

    For example: If volume passes 100 million rows or hosting costs double.

  • Related decisions and linksoptional

    For example: Replaces ADR-0004. Related: ADR-0009.

IT and projects

What is inside

The parts of this document, in order.

  1. 1Context
  2. 2What matters most
  3. 3Options considered
  4. 4Decision
  5. 5Why
  6. 6Consequences
  7. 7When to revisit
  8. 8Related

Templates

How it works

  1. 01

    Fill in

    Type your details in the form. The document fills itself in as you type; click any gap to jump to its field.

  2. 02

    Check

    Read it through. Gaps you have not filled stay marked, so nothing goes out half done.

  3. 03

    Download

    Save it as a Word document to edit further, or as a PDF to send or print.

Make it yours with AI

Open it in the chat and ask for changes: shorter, firmer, another situation, another language.

Adapt it with nerix

IT and projects

Questions people ask

What details does this template ask for?

The form asks for 13 details, starting with Record number, Decision title, Status, Date, Decision makers. 2 more are optional.

Can I download this template as Word or PDF?

Yes. When you have filled in the form, save it as a Word document to keep editing, or as a PDF to send or print. It is free and needs no account.

Is what I type sent anywhere?

No. What you type stays in your browser while you fill in the document. It only goes to nerix if you choose to open the template in the chat.

Are these IT and project templates free?

Most are. Fill in and download them for free as Word or PDF, with no account. A few longer documents are premium: free to fill in, paid once to download, and marked with their price.

Does a security policy make us secure?

No document does that alone. A policy helps when it matches what people really do, so keep it short, explain it to your team and review it every year.

Is a project charter only for large projects?

No. A small project benefits too, because one page that names the goal, the limits and the decision maker prevents most arguments later.