Hanami – web framework for Ruby

It was a good name, too.

I definitely hadn't heard of it until his post. Prior to that, only really knew of Rails and Sinatra as Ruby frameworks.

Which came first, this or Phoenix (for Elixir)? The design seems very similar.

Thank you! They changed the whole site so I thought Hanami popped up from nowhere. I checked it out when it was still called Lotus, looked really interesting. Good to see this project gaining ground.

Have you tried Padrino? Of all the frameworks I've tried in the past 10 years, this is as good as it comes. Love the Sinatra + Sequel + erb setup as it is simple and straightforward. Fast and elegant without the Rails lockdown architecture. http://padrinorb.com/

May not be a fit for the situation you describe, but mounting a Sinatra app inside a Rails app (or mounting it at the Rack level) can be a solution. I think more people come at it the opposite direction you describe: start with Rails, and build out smaller apps in Sinatra when Rails feels too heavy.

Have you looked in to Padrino? http://padrinorb.com

You can cherry pick parts of it out in to a Sinatra app, or you can swap out `Sinatra::Application` for `Padrino::Application`.

You might want to check out Padrino (http://padrinorb.com). My understanding is that it is built on Sinatra, but makes it easier to add some of the Rails-like functionality in a more modular manner.

+1 for Padrino - I've cut all my recent apps in it and it is superb. I can even use 90% of Rails gems in there (exception being those that are ActiveRecord specific, seeing as I use DataMapper or Sequel)...

I've played around with it and Hanami seems to be targeting the larger complex apps that eventually become become painful with Rails due to fat models / controllers among other things.

Hanami seems to be inspired by Uncle Bob's Clean Architecture. IMO it's pretty nicely done and a good example of how Clean Arch can be implemented. Worth playing with if only to get a feel for it's structure and potentially influence your Rails apps.

From my experience it is still pretty alpha quality. I ran into a weird issue with the inflector library they rolled themselves and had to dig through the code to figure out what was going on. This was about a month ago, so things could have changed, but I wouldn't recommend this for production app just yet. At least one that you have a timeline on.

Should be able to use Rack middleware like Warden.

>what problem does it solve?

it's not rails.

In essence it tries to be a framework like Rails, in that it is all inclusive, but without all the "magic" that has been discussed about Rails lately.

Most things are just plain old ruby objects and you include the modules you need. This is an oversimplification, but for example: When I build out controller actions in a Rails app, I typically will break out complex actions into service/action/command classes. This allows me to test the logic in isolation from the controller, and allows for true unit tests without need to actually make real requests. Hanami, on the other hand, right from the get go, makes actions there own classes for this very reason.

Also the idea of an "Application" is a bit more vague. Your main app is more a meta-app. This, in theory, helps you develop separate service like applications that are then mounted within this meta-app. This may make it easier to break out into actual services later on.

If you just follow "Rails conventions" and the app is long living, it can get pretty damn unwieldy. I guess the idea here is you can follow Hanami conventions and the app will be more maintainable even at large sizes.