Hanami - New Ruby Web Framework
summary
Hanami claims modular, lightweight apps built from ten gems and actually runs as independent apps inside one project so you can boot only the admin service; it uses ROM with a repository pattern and immutable entities, actions are one-class-per-endpoint with a single public method called `call`, view objects pair with templates, testing treats actions as plain Ruby objects, thread-safe and no global monkey‑patching, remaining issues are spotty docs and a few missing gems (CLI fix targeted in 1.1).
AI-written summary · about
chapters (15)
- 0:00Introduction
- 2:26Modularity
- 5:04Applications
- 7:00Business logic
- 8:08Difference between Hanami and others
- 9:43Controllers
- 11:07Models
- 13:15View
- 14:07Proxy
- 15:36Pros
- 16:07Why its so cool
- 16:28Cons
- 17:58Gems
- 19:00Resources
- 20:07Questions
related talks
25mHanami - New Ruby Web Framework
42mHanami - New Ruby Web Framework
31mHanami 2: New Framework, New You
50mWhat I Talk About When I Talk About Ruby
23mHanami 2: New Framework, New You
39mSlicing and Dicing Through Complexity with Hanami
36mReturn To Simplicity: Architect Hypermedia REST applications using Hanami + HTMX
47mLivin’ La Vida Hanami