Engineering Decision Records

Decisions.

Public architecture decisions in ADR format — context, options considered, decision, rationale and consequences. Generic examples with no client reference: this is how we arrive at decisions that hold.

ADR-001Accepted
Modular monolith as the starting point, microservices on evidence
New systems start as a modular monolith with explicit module boundaries. Individual services are extracted only when a concrete requirement justifies it.
ADR-002Accepted
Queues instead of synchronous processing outside the critical path
Side effects outside the critical response path run asynchronously via a queue. The request acknowledges quickly; processing happens idempotently in the worker.
ADR-003Accepted
Normalized tables over JSONB in PostgreSQL
Core entities are modeled in normalized form, with constraints and foreign keys. JSONB is used selectively for genuinely schemaless or rarely queried peripheral data.

Decisions.

Modular monolith as the starting point, microservices on evidence

Queues instead of synchronous processing outside the critical path

Normalized tables over JSONB in PostgreSQL