Art of Domain Modeling
summary
Argues that domain quality is the leading indicator for maintainability and feature speed and gives a concrete workflow: iterate early while it's cheap. Uses a pizza-shop example with precise invariants (toppings always add cost; add then remove is a no-op), Clojure-style function signatures, a runnable specification implemented in-memory, and property-based tests. Adds abstract non-domain concerns like immutability, event sourcing, concurrency, then maps to real implementation choices (enums, multimethods, database) guided by volatility analysis.
AI-written summary · about
chapters (6)
- 0:00Intro
- 0:23Why do we model
- 2:13Software design
- 8:03Domain complexity
- 10:22Abstract
- 18:53Implementation
related talks
51mDomain Modeling Made Functional
01h 05mFrom object oriented to functional domain modeling
46mAlgebraic Thinking for evolution of pure functional domain models
49mDomain Modeling Made Functional
52mFunctional Patterns in Domain Modeling
46mDesign for errors - An introduction to Domain Modeling with a bit of Arrow
34mHow I learned to stop worrying and love Functional Design
39mFunctional Architecture for the Practical Rubyist
