Monolith

A single deployable unit containing all functionality. Simplest to build, test, and deploy at small scale.

Why we need this / what value this brings

Simplest to build, test, deploy, and reason about — one codebase, one deploy, no network calls between your own components.

When to use this

Default choice for a small team and an application that isn't yet hitting monolith-specific pain (deploy contention, needing to scale one part independently).

How to use or implement this

Keep internal module boundaries clean even inside the monolith (see ModularMonolith) so a future extraction, if ever needed, isn't a rewrite.

Research questions

• What's the actual failure mode of a monolith at scale (deploy coupling, blast radius) vs the myth of it?

---

Empty folder — drop notes, links, and findings here as you research.