3 ms·
We've built web applications based on Django for small CMS sites, large multi-language CMS sites, up to large custom-built applications (mostly API-based) for t
by jonasvp 10y ago
We've built web applications based on Django for small CMS sites, large multi-language CMS sites, up to large custom-built applications (mostly API-based) for the likes of Mercedes-Benz and Deutsche Bahn. I can honestly say that I never regretted the decision.
It scales beautifully (see the likes of Instagram, Disqus, Sentry, etc.), has a great security track record, sane deprecation schedules, and the core team keeps up with the times and new technologies but does so at a sane pace and without rushing things.
Not to mention the documentation - ohmygod, the documentation!
In a nutshell: pick Django, keep learning Python, and try to build something that your users love.
- stefantalpalaru 10y ago> It scales beautifully It wastes resources, both CPU and RAM, so scaling is usually throwing more hardware at the problem instead of rewriting the whole thing in a more efficient language/framework. > has a great security track record Does it really? How many of us are stuck on old and vulnerable Django versions because our clients won't pay for the increasingly non-trivial job of upgrading to the latest backwards-incompatible version? > the core team keeps up with the times and new technologies but does so at a sane pace and without rushing things That's a nice way to spin it.
- tedmiston 10y agoI've stopped citing Instagram as an example of Django scaling after learning from one of their engineering managers at PyCon 2015 that they're running a heavily modified internal fork of Django 1.5 or 1.6. It sounds like they really have built their own framework (before today's Django + DRF existed). Maybe this has changed post Facebook acquisition. I know Facebook is mostly on Python 3 and modern stuff now.