Break Apart Rails Monoliths
bluebox.net
The framework is a servant of the application, yet the app becomes constrained by it.
A simple rule: Business logic should go elsewhere.
bluebox.net
A simple rule: Business logic should go elsewhere.
When I was working with frameworks in the past it was always a temptation to allow the framework to dictate the application organization. The discipline to not do this required me to understand the framework and how to bend it to my will. I wonder if this is a problem that others run into and thus get "trapped" in the framework?