interactor

Been doing Rails development for 6+ years. The most maintainable codebases I've worked on had some kind of service layer between the controller and the model. We used the "interactor" gem to create individual units of business logic that we could reuse and piece together into larger "flows". Business logic stayed in the interactors, persistence logic in the models. This lead to skinny controllers, skinny models and many, many many reusable skinny services. One fortunate side effect is that all these pieces became extremely easy to test in isolation, as well as integration tested. https://github.com/collectiveidea/interactor

Yes, ActiveRecord is not a good pattern for large-scale apps. The reason it's in Rails is because it's very good for simple cases and prototypes. But there is absolutely nothing in Rails stopping you from adding a service layer in whatever shape you see fit, I'm a fan of interactors (https://github.com/collectiveidea/interactor), but use whatever you want, it's easy to plug in new directories into the app structure and get magic loading and spec running automatically. I agree that Rails enables a lot of messes, but I don't think the solution is to make your framework prescriptive about every single detail. I'd rather have the flexibility and enforce some standards per project than expect the framework dictate everything, because once you hit scale you have to do your own thinking and architecture anyway.

I used this for a huge project with a lot of states. Separated my workflow out into individual files for each class so they could just be included at the top. Then for each transition method, I created a service object (Interactor gem[1]) to handle all of my complicated transition logic, so the object-level transition methods would just check for a success or failure and perform the transition appropriately. Really love how it turned out. [1] https://github.com/collectiveidea/interactor

I'm not going to argue. However if you've run into the same problem where you feel like you need to either make fat model or fat controller in Rails, here's a simple solution: https://github.com/collectiveidea/interactor

What's the different between interactor and wisper? Wisper is better doing the job in your example. interactor: https://github.com/collectiveidea/interactor wisper: https://github.com/krisleech/wisper