A Contrarian View of Software Architecture
summary
Argues that prescriptive layered styles like Clean/Onion lead to shotgun surgery, database chattiness and brittle code in long‑running systems (5–10+ years), because repository abstractions force lowest‑common‑denominator CRUD and hide transaction boundaries. Demonstrates practical alternatives using vertical slice architecture and an A‑frame pattern, with concrete tooling: integration tests run against Dockerized databases and examples using Marten and Wolverine to keep business logic infrastructure‑free and enable incremental, feature‑by‑feature upgrades.
AI-written summary · about
chapters (12)
- 0:00Introduction
- 0:18Who is Jeremy
- 1:35Jasper FX Software
- 2:04Large Systems
- 5:12Everything Works Up Front
- 10:12Clean Architecture
- 11:03Layered Architecture
- 12:27Problems with Layered Architecture
- 19:01Reference Architecture
- 25:01Gen X
- 29:38Obstruction
- 37:01Review
related talks
52mEvolving a Pragmatic, Clean Architecture A Craftsman's Guide
50mTowards an Evolutionary Architecture
01h 29mArchitecture Beyond Clean & Hexagonal
08mLightning talks – 101 Things Software Never Learnt
44mDeliberate Architecture
37mArchitecting for Tomorrow: A Pragmatic Perspective
33mSet Design: Putting the "Art" in "Architecture"
45mFive things every developer should know about software architecture