Functional Architecture for the Practical Rubyist
summary
Argues that modeling behavior as small functional objects (a single call method) and data as immutable value objects yields code that satisfies SOLID, eases testing with dependency injection and mocks, and produces a directed acyclic dependency graph. Shows an import_products example wired to download_feed and products_repository, tests it with doubles, and uses dry-system plus dry-types/validation for wiring and types. Reports building 10+ apps over two years with this architecture and finds it works well.
AI-written summary · about
chapters (10)
- 0:00Introduction
- 1:03Functional architecture shift
- 3:46Functional objects
- 7:28Handling data with types
- 9:18SOLID principles and design
- 15:17Testing and dependency graph
- 18:25Emergent modular architecture
- 20:57Tooling and dependency injection
- 24:21Conclusion and summary
- 26:28Q&A session
related talks
39mFunctional Architecture for the Practical Rubyist
35mReal-world Functional Ruby
44mReal-World Functional Ruby
41mAPPLICATION ARCHITECTURE: BOUNDARIES, OBJECT ROLES, & PATTERNS
42mTaking inspiration from the functional world
27mFunctional Ruby and the (big) dependency diet
26mBlending Functional and OO Programming in Ruby
40mReinvesting in Ruby