Hanami is a Ruby MVC web framework comprised of many micro-libraries. It has a simple, stable API, a minimal DSL, and prioritises the use of plain objects over magical, over-complicated classes with too much responsibility.
The natural repercussion of using simple objects with clear responsibilities is more boilerplate code. Hanami provides ways to mitigate this extra legwork while maintaining the underlying implementation.
Here are three compelling reasons to choose Hanami:
Hanami's code is relatively short. It only concerns itself with the things that all web applications—regardless of implementation—need.
Hanami ships with several optional modules and other libraries can also be included easily.
If you've ever felt you're stretching against the "Rails way", you'll appreciate Hanami.
Hanami keeps controller actions class-based, making them easier to test in isolation.
Hanami also encourages you to write your application logic in use cases objects (aka interactors).
Views are separated from templates so the logic inside can be well-contained and tested in isolation.
Making use of threads is a great way to boost the performance of your application. It shouldn't be hard to write thread-safe code, and Hanami (whether the entire framework, or parts of it) is runtime threadsafe.
The guides explain high level Hanami components and how to configure, use and test them in a full stack application. The imaginary product that we'll mention is called "Bookshelf": a online community to share readings and buy books.
We have a getting started guide, to build our first application with Hanami.