Use Case Driven Development
summary
Claims Rails’ default model-driven layered approach fails when the domain is hard to model or the app grows; proposes adding a clear use-case layer (UE-space) plus persistence/repository layers to decouple the web framework from a single business core. Describes experiments that turn business logic into a testable object, allows horizontal growth toward bounded contexts and microservices, and trades simpler initial development for explicit engineering choices and risk of a heavyweight monolith.
AI-written summary · about
chapters (9)
- 0:00Introduction
- 0:45System architecture
- 2:12Complexity and abstraction
- 3:23System types
- 4:27Architectural styles
- 5:55Architecture style examples
- 7:01Layered architecture in Ruby on Rails
- 8:47System growth
- 10:14Learning principle and conclusion
related talks
44mBuild to Last...
18mA Case for Use Cases
36m"Business Logic in Ruby"
43mThe Clean Architecture: How to Grow From Startup to Enterprise
38mWhat I talk about when I talk about Domain Driven design
35mBuild Complex Domains in Rails
34mSustainable Architecture
30m15 Years of Rails With Domain Driven Design - Lessons Learnt