At my company, we’re three developers maintaining a codebase that has been developed “Fat models” style.
We’re currently refactoring our codebase to an architecture resembling the Clean Architecture, and though it is a lot of work we’re already seeing benefits in terms of testing.
Our platform is basically a dashboard with financial data, the model domain is pretty complex and there is not a lot of CRUD functionality available (most use cases are reads + lots of calculations on the fly). In cases like these I think services / use cases layer approach works great.
I have a bunch of links that I’d like to share to resources we’ve used to inform our decisions, but I can only post two since I’m a new user:
Django model Guideline
Business Logic in Django projects
I think this is a very interesting topic and I’d be glad to discuss more details regarding our own approach if anyone is interested. I’m also looking forward to reading Harry Percival’s book on architecture which can be found on github. If anyone is interested in the rest of the links to other articles and talks about architecture just get in touch and I’ll send them.