Responsibility Driven Design Revisited
summary
Claims Domain-Driven Design is incomplete without Responsibility-Driven Design and shows how to find behavior first, then assign roles and responsibilities into collaborating objects. Demonstrates a lightweight process: write a design story, extract themes, create candidates, map responsibilities on CRC cards, then play the ball-passing game to reveal missing objects and contracts. Recommends delegated control styles, object neighborhoods, and using interfaces; cites Brighter as a battle-tested .NET messaging framework sending over 1.5 billion messages a day.
AI-written summary · about
chapters (6)
- 0:00Introduction to RDD
- 1:57Domain Driven Design basics
- 8:18What is responsibility driven design
- 23:08CRC cards and modeling
- 36:47CRC card game walkthrough
- 43:04Summary and Q&A
related talks
48mDomain-Driven Design tactically and practically
55mDomain-Driven Design: back to the roots
41mDomain-Driven Design: Hidden Lessons from the Big Blue Book
38mWhat I talk about when I talk about Domain Driven design
47mDomain-Driven Design: A Complete Example
49mHow to cook Domain Driven Design
31mIs Domain-Driven Design Overrated?
58mImplementing Domain Driven Design as a Pragmatic .NET Developer