Engineering· 6 min read
The case for boring architecture
A monolith, a relational database and a handful of well-understood tools will carry most businesses further than anyone expects.
NNAFATECHS AdminAdministrator
Every few years a new architecture arrives with a conference talk and a promise. Microservices, serverless everything, event sourcing, the data mesh. Each is the right answer to a real problem — and each is regularly adopted by teams who do not have that problem. When we start a new engagement, our default is deliberately unfashionable.
Start with one deployable
A well-structured monolith has one thing distributed systems cannot match: a function call is reliable. There is no network between your modules, no partial failure to design around, and one deployment to reason about. Clear module boundaries inside the codebase give you most of the benefit of services, and leave the door open to extract one later if a real scaling or ownership reason appears.
Let PostgreSQL do more
PostgreSQL handles relational data, JSON documents, full-text search, queues and geospatial queries competently. Before introducing a second data store, we ask what Postgres cannot do for this workload. Usually the honest answer is “nothing yet”, and every system we do not add is one fewer to secure, back up, monitor and understand at 3am.
Spend complexity where it pays
Boring is not the same as simplistic. We still invest in the parts that matter to your business: the data model, the test suite, the deployment pipeline and observability. The point is to concentrate complexity where it creates value, rather than spreading it across the stack because it seemed modern.
When we choose differently
We reach for something more elaborate when the evidence demands it: independent teams who need independent release cycles, workloads with genuinely different scaling profiles, or compliance boundaries that require isolation. The rule is simple — complexity must be paid for by a problem you can point at.
The result is software your next hire can understand in a week, which is the quiet measure of good architecture.
