4 ms·
> Hide the ORM behind Repository interfaces > Marshall ORM objects into true Domain objects > Do not call to the database in the HTTP adapter/validators The
by tmp_anon_22 5y ago
> Hide the ORM behind Repository interfaces
> Marshall ORM objects into true Domain objects
> Do not call to the database in the HTTP adapter/validators
The tradeoff for this is exploding the number of files, directories, and tests, needed for the project. Which has its own cost and overhead.
- berkes 5y agoI'm not experienced in Django. But doing this in Rails is very hard. It goes against the most strongest of opinions this opinionated framework has. So much, that if you strive for such a design (and you should, IMO) Rails is more in the way than helping you - I know, I tried.
- skrtskrt 5y agoSure, writing boilerplate is always going to have overhead. But in my experience the stricter-yet-more-verbose design strongly increases maintainability and velocity in the long term, which should be self-evident due to the massive reduction of coupling.