Given the characteristics of Flask , Tornado and Django ,
- Flask features: lightweight, concise, extensible
- Tornado features: mainly asynchronous mechanism
- Django's features: Yamato, orm, template, and view all come with them
If you are developing a REST API system without complex layers and logic, Flask will be a good choice, because the built-in functions of the framework are enough for you to complete this task; or, you are planning to implement a large-scale system, you need to re-implement most of the plug-in content by yourself, Flask is also good, because it is simple enough, allowing you to quickly read and expand.
In other cases, I still recommend that you use Django . Especially when you need to install a lot of Flask plugins to implement Django
Tornado 's good results are due to its own asynchronous features, while Django and Flask are synchronous frameworks , and their performance is limited when processing requests. But in actual use, it is generally the mode of Django/Flask + Celery + Redis/Memchaned/RabbitMQ , which brings the ability of asynchronous processing .