The courage to business logic - Business Driven Architecture
summary
Codebases hide business rules under layers, generators and helpers and that causes duplicated date/zip/name logic appearing in hundreds of places. The concrete fix is threefold: replace primitives with value objects (immutable, validation, conversion), model domain state with rich entities (methods not setters), and use a Builder to avoid constructor hell. Examples target Java EE: JSF-compatible builders and JPA embeddable value objects, which reduces utils, prevents inconsistent states and makes business intent readable and maintainable.
AI-written summary · about
chapters (9)
- 0:00Introduction
- 1:30Problem with business logic
- 5:01Reality check with code examples
- 23:22Goal of meaningful domain model
- 24:45Value objects in domain model
- 34:47Rich entities explained
- 42:58Builder pattern for consistency
- 49:07Code as the design
- 51:37Q&A session
related talks
50mThe Anatomy of Business Conditions
52mBreaking Bad Code: From simple problems to complicated solutions and back
59mDomain-Driven Design - Where Rubber Meets the Road
52mEvolving a Pragmatic, Clean Architecture A Craftsman's Guide
01h 01mClean Architecture
51mA Clean, Pragmatic Architecture
36m"Business Logic in Ruby"
11mUse Case Driven Development