Decoupling Your Business Logic from the Django ORM

Where should I keep my business logic? This is a perennial topic in Django. We can imagine a continuum of cases, with increasing complexity: I begin with my...

The Stack Report
@carlton disregarding specific libraries, there's definitely a rich discussion to be had around application architecture and complexity management here, and I think your entry here adds to it thoughtfully. I personally fall into the camp where I'll happily put the business logic meat into the "view", eschewing a service layer until the codepath needs to be shared. I have folks at $DAYJOB arguing otherwise, and not without merit.

@carlton the argument goes that refactoring into a more abstract service layer on-demand runs into the risk of it being done inexpertly and inconsistently. Which I understand.

I guess, like many things in software engineering, the right call here depends on the people involved and not the technical arguments one way or another