Concepts & principles / principle
Prefer the least complexity that genuinely satisfies the whole system’s requirements.
A static site is simple for public publishing. A database may be simpler for concurrent transactional updates. Judge the whole system: maintenance, security, recovery, cost, and the knowledge required to operate it.
Cheap code generation does not make dependencies or operational state free. Ask what each layer contributes, what owns its state, and how it can be removed. Prefer explicit, understandable mechanisms over speculative flexibility.
Part of a connected world
The complete semantic record, rendered from root node: front matter.
semantic_node:
description: Prefer the least complexity that genuinely satisfies the whole system’s requirements.
id: simplest-capable-architecture
kind: principle
name: Simplest-capable architecture
relationships:
- predicate: supports
target: builder-sovereignty
- predicate: applies-to
target: build
type: concept
description: Prefer the least complexity that genuinely satisfies the whole system’s requirements.
draft: false
title: Simplest-capable architecture
url: /graph/concepts/simplest-capable-architecture/