"Consequential Clojure Architectures"
summary
Catalog of common Clojure anti-patterns and concrete fixes: massive 5,000-line namespace causing duplication and cyclomatic complexity, HTTP handlers that inline business logic instead of delegating, and overuse of clojure.spec at every call site (use it at system boundaries only). Replaces ORM-like records with plain maps + next.jdbc or multimethod dispatch, models UI with atoms + watches for MVC, and recommends hexagonal architecture / Polylith and the Strangler pattern to split services.
AI-written summary · about
chapters (4)
- 0:00Start
- 1:16Consequential Clojure Architectures Definition
- 7:20Software Architecture Anti-Patterns
- 23:43Software Architecture Patterns
related talks
26mDependency Management in Clojure
30mIntroducing structure in Clojure
35mThe League of Extraordinary Antipattern
51mA Clean, Pragmatic Architecture
24mBuilding Intelligible Systems
43mArchitecture antipatterns and how to beat them 1/2
52mEvolving a Pragmatic, Clean Architecture A Craftsman's Guide
30mGrowing Clojure Systems. From Functions to Microservices