Flask vs django
| Parameters | django | Flask |
|---|---|---|
| Framework type | Full stack web framework | Micro framework |
| Database | SQL : MySQL, Oracle | No SQL : mongo DB |
| Data models | ORM (object-relational mapping) | N/A |
| Project size | Large project with potential for growth in future. high-load applications | Small and less complected project |
| Project layout | Conventional | Arbitary |
| Application type | Full featured | Static |
| Performance | Better | |
| Flexibility & control | built-in features and modules, offers far less freedom and control. | minimalism and simplicity. No restrictions |
| Security | Cross-site scripting (XSS), Cross-site request forgery (CSRF), SQL injection | Cross-site scripting (XSS), Cross-site request forgery (CSRF), SQL injection |
| Community | huge active developer community | not as big |
| Learning curve | steeper learning curve | |
| Ready to use admin | Yes | No |
| Maturity | release in 2005 | release in 2010 |
| Used by | Instagram, pintrest, udemy, Dropbox, Spotify | Netflix, lyft, redit, Airbnb, Rackspace |
Which framework to choose?
Performance |
High |
Flask |
Low |
Django |
|
Size of the project |
Large |
Django |
Small |
Flask |
|
Structure |
highly customisable |
Flask |
Satisfied with built-in features & modules |
Django |
|
Type of project |
Simple |
Flask |
Complex |
Django |
|
Changing Project Requirment |
Dynamic |
Flask |
Static |
Django |
|
Codes |
More lines |
Django |
Few lines |
Flask |
|
Time and Budget |
Limited |
Django |
Not limited |
Flask |
|
Suitable for |
Web sites/Web application |
Django |
Fully custom web application |
Flask |