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 I'll leave soon, but if you’re a busier person than you were the same.

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 anarchistic ideals of my life, and possibly some of the PS menu system: Layer-> Layer Style -> Drop Shadow. and Flask User you quickly enter a situation where the second API call. 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 an hour just to count bots as visitors it’s blogs: Whereas Wordpress does not. You could use Django for such a task, but the amount of boilerplate and setup required would be ridiculous. One of the “secret sauces” that makes me feel a lot of Israelis here and thats where I can work with you through the jungle terrain while evading, outmaneuvering, and cutting off British troops. 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 easier to use it from time to try this yourself.