search for: acts_as_taxable

Hi, Given the convention of fat models to handle business logic, is there a point where you might be justified in using a separate plain ruby object(s) to orchestrate certain business logic interactions, essentially a middle layer between your controllers and models for high level functions? If you look at the InventoryTransaction model below you will see the sort of methods I mean. In this case