4 ms·
For what it’s worth, on a Django codebase of 180k lines, 100k lines of templates, 1000 URLs, 380 “apps”, 350 models, we have a nice coherent structure across th
by danpalmer 8y ago
For what it’s worth, on a Django codebase of 180k lines, 100k lines of templates, 1000 URLs, 380 “apps”, 350 models, we have a nice coherent structure across the whole codebase that makes us really productive.
I haven’t seen a Flask code bass do this anywhere near as well. They all seem to end up becoming very different and tricky to onboard new devs onto because they are so custom.
Django hides some complexity, but we haven’t found many pets we can’t effectively customise, and the architecture at scale is great, something I haven’t seen in many other places.
- travisjungroth 8y agoWhat does that Django project do?
- danpalmer 8y agohttps://www.thread.com/ https://www.thread.com/ Curated ecommerce, a CRM like system for stylist, order management, fulfilment and distribution.
- ernesto7 8y agoDo you mind explaining what that structure is? I always find the standard Django structure of everything is an "app" difficult to navigate once the codebase gets larger.
- danpalmer 8y agoAs much as I'd rather not plug my own talk, it's probably going to give you more information than I could ever get in a reply here. https://thread.engineering/scaling-django-codebases-pycon-uk-2017-91c166fcb926 https://thread.engineering/scaling-django-codebases-pycon-uk...
- jnbiche 8y ago> I haven’t seen a Flask code bass do this anywhere near as well. They all seem to end up becoming very different and tricky to onboard new devs onto because they are so custom. While some Flask web applications may use different file organization schemes, any large app will use blueprints. Blueprints are fairly standardized and easy to understand. I personally find Flask blueprints easier to follow than Django apps, but they're pretty similar.