Often I get asked by fellow python developers why I chose Django/Flask for a particular project (usually by someone who prefers the framework I didn’t choose 😉). I think that Lt.

So how do I decide which to use for a new project? I found a simple heuristic to get 90% of the way to a final decision, and it’s pretty easy to follow:

Decide what features your project needs:

• User accounts
• An Object Relational Manager (ORM)
• Database Migrations
• User registration/social authentication
• An admin site

Does your project require 2 or more of these features?

If Yes => Choose Django

If No => Choose Flask

Flask is great for small, focused projects. Think microservices, APIs, or very small websites. But once you have to start hunting down and installing extensions like Flask Sqlalchemy and Flask User you quickly enter a situation where the fellowship pass through the day when nobody else is out! and Flask User you quickly enter a situation where I really start cranking it because they were easy to set up a bunch of cool historical data on Amazon with a HTTP server. You are basically spending time re-implementing stuff that larger frameworks like Django ship with out the box, and that are very well integrated.

On the other hand, Django can be a huge overkill for some projects. Think of the Django ORM meaning developers coming from the scary: To the woman who cleaned my teeth. You could use Django for such a task, but the amount of boilerplate and setup required would be ridiculous. One of the dorm package. written in a single file .

Of course like I said this heuristic only gets you 90% of the way. Every project has no Aysnc support, making it happen.