Slicing and Dicing Through Complexity with Hanami
summary
Hanami claims a feature-first modular monolith: slices are mountable and even independently deployable, letting billing live isolated from auth while integrating through explicit interfaces. The stack uses ROM + dry-rb for persistence and operations: relations return immutable structs, repos materialize with to_a/one, and dry-monads yield success/failure flows. Actions are single-class callables, views are plain Ruby parts, and memoizing actions shows an observed 8× speedup in request handling.
AI-written summary · about
chapters (13)
- 0:00Introduction to Hanami
- 0:31Philosophy and core components
- 6:06Beyond traditional MVC
- 8:41Story and design differences
- 13:05History of the framework
- 13:54Hanami architecture overview
- 16:20Slices and containers
- 21:38Dicing up MVC: Actions
- 25:37Views, parts, and context
- 27:37DB layer and repositories
- 32:13Operations and testing
- 33:53Rails integration and performance
- 34:27Community and conclusion
