Tips for Building High-Quality Django Apps at Scale
This reads way more like a list of Django caveats and anti-patterns, than a guide to running any kind of Python application at &quot;scale&quot;. Maybe a sprinkling of good hygiene, but that has nothing to do with scalability (unless you&#x27;re talking about developer scalability and cognitive overhead).<p>Further, to suggest NOT using the ORM and to build out a middle layer on top of the ORM just for CRUD, is, well, insanity.
On one hand the author is saying to cut down on bloat, and then on the other hand they are saying to add needless abstraction on an already bloated ORM.<p>I don&#x27;t use Django, but I do use Python for application development nearly every day, and I have to say... this article reads more like a list of (predictable and basic) problems their team had than a guide to scaling an application. Maybe they mean, how to scale their team, workflow, and their efficiency, NOT the application itself.<p>The only thing I agree with here is the avoidance of some Django features... However, they should take it a step further, and just avoid Django in the first place.<p>Also, am I the only one that has never needed to use &quot;migrations&quot; or any similar sorts of features? You&#x27;re doing something very wrong and overcomplicating things if you seriously need to lean on migrations that heavily.