I'm not suggesting that you should create modules and include these into your ActiveRecord-models. Feel free to create any kind of class/module/object/whatever, but as long it's related to the business logic put it under app/models.
Re:Rails is not your application
by saturnflyer on Sunday October 23, 2011 @09:53AM
(#3146115)
+1 app/models is for domain models
Now somebody is browsing your code and they are ripping their hair off, because there's a method on Order object and there are 6 modules included in the Order object.
Before you realize it, you're violating not only MVC but also OOP.
If you used Services, you could model nice controller/manager classes in OOP manner, with responsibilities nicely distributed. These are your controllers. Rails controllers are just the HTTP interface.