Need advice about which tool to choose?Ask the StackShare community!
Flask vs Tornado: What are the differences?
Introduction
Here are the key differences between Flask and Tornado:
Execution Model: Flask is built on a traditional threaded model where a new thread is created for each request, allowing multiple requests to be processed simultaneously. On the other hand, Tornado is built on a non-blocking asynchronous model with an event loop, allowing it to handle many simultaneous connections efficiently.
Web Server: Flask does not include a built-in web server and requires a separate web server, like Gunicorn or Apache, to handle HTTP requests. Tornado, on the other hand, comes with a built-in web server and can handle HTTP requests without the need for an additional server.
Scalability: Flask is better suited for smaller applications and websites with low to medium traffic, as it relies on multiple threads for handling requests. Tornado, with its asynchronous model, is better suited for high-performance applications that require handling a large number of concurrent connections and real-time functionalities.
Framework: Flask is a micro-framework that provides just the essential tools for building web applications, allowing developers to have more control and flexibility. Tornado, on the other hand, is a full-featured web framework that provides a wide range of tools and functionalities, including support for websockets, authentication, and templating.
Compatibility: Flask is written in Python and can be used with any Python web server or deployment option. Tornado, on the other hand, is also written in Python but is specifically designed to take advantage of non-blocking I/O and can be used as a standalone web server or integrated with other Python frameworks.
Learning Curve: Flask has a simpler and more straightforward learning curve, making it easier for beginners to get started with web development. Tornado, on the other hand, has a steeper learning curve due to its more advanced and asynchronous nature, making it more suitable for experienced developers or those who require high-performance applications.
In Summary, Flask is a micro-framework focused on simplicity and flexibility, while Tornado is a full-featured asynchronous web framework with high-performance capabilities.
My journey to developing REST APIs started with Flask Restful, and I've found it to be enough for the needs of my project back then. Now that I've started investing more time on personal projects, I've yet to decide if I should move to use Django for writing REST APIs. I often see job posts looking for Python+Django developers, but it's usually for full-stack developers. I'm primarily interested in Data Engineering, so most of my web projects are back end.
Should I continue with what I know (Flask) or move on to Django?
If you want to be a Web developer with knowledge in another frontend and NoSql technology, maybe continue with Flask. However, if you want to create very fast solutions to grow up with a new business and merge these with data analysis and other tools, Django is the answer. Basically read more about the service architecture where you feel more comfortable, Microservice or Monolithic, but please will not married with any because they solve issues to different contexts.
Which is the best Python framework for microservices?
We are using Nameko for building microservices in Python. The things we really like are dependency injection and the ease with which one can expose endpoints via RPC over RabbitMQ. We are planning to try a tool that helps us write polyglot microservices and nameko is not super compatible with it. Also, we are a bit worried about the not so good community support from nameko and looking for a python alternate to write microservices.
Bottle is much less bloated and fast. Its built-in templating system is one of the fastest as it compiles the templates in bytecode. Also Bottle has no depenencies, preventing dependency bloat.
I have just started learning Python 3 weeks ago. I want to create a REST API using python. The API will be used to save form data in an Oracle database. The front end is using AngularJS 8 with Angular Material. In python, there are so many frameworks to develop REST APIs.
I am looking for some suggestions which REST framework to choose?
Here are some features I am looking for:
Easy integration and unit testing, like in Angular. We just want to run a command.
Code packaging, like in java maven project we can build and package. I am looking for something which I can push in as an artifact and deploy whole code as a package.
Support for swagger/ OpenAPI
Support for JSON Web Token
Support for test case coverage report
Framework can have features included or can be available by extension. Also, you can suggest a framework other than the ones I have mentioned.
For starters flask provides a beautiful and easy way to create REST APIs. Also its supported by excellent beginner docs as well as a very active community. Another good thing with Flask is its widely available list of plugins which allow you to build as you go. Its also good in performance and can scale to a quite decent level. However, if you are sure your project is going to be fairly big, it would be better to start with Django as it provides a lot of features out of the box and is extremely stable in performance. Both these frameworks have support for Swagger, JWT, Coverage Report although you have to install plugins for them. Deploying both of these are fairly simple and there is huge documentation available. Django has one of the best documentations I have come across. I hope I was able to answer your queries.
I have a microservice architecture where I have multiple storages and services and it will be expanding on the go adding more microservices and each microservice will be contained in a docker container and for microservices orchestration, Kubernetes is going to be used but I'm not sure if I should do them in flask or tornado
I would choose flask over tornado if you want to create easy back ends. Once you are looking for scalability, tornado offers great async operations like nodejs.
If in doubt, go with flask.
Speed: tornado Large community & documentation + easy: flask
But what are you building??? It really depends on that, if you are building an web app I would recommend you Flask, If you are building RESTful service that heavily relays on I/O then Tornado as an async framework, but if you need sync you can use Bottle. If you can provide us with more details about your service we could give you better advice.
Without knowing your exact requirements, Iʼd recommend Flask. Tornado is excellent when it comes to async stuff, but Flaskʼs extension ecosystem is much broader. Unless you can afford developing some small but significant parts of your app, you will have an easier life with Flask.
Pros of Flask
- For it flexibility10
- Flexibilty and easy to use9
- Flask8
- User friendly7
- Secured6
- Unopinionated5
- Secure2
- Customizable1
- Simple to use1
- Powerful1
- Rapid development1
- Beautiful code1
- Easy to develop and maintain applications1
- Easy to setup and get it going1
- Easy to use1
- Documentation1
- Python1
- Minimal1
- Lightweight1
- Easy to get started1
- Orm1
- Not JS1
- Perfect for small to large projects with superb docs.1
- Easy to integrate1
- Speed1
- Get started quickly1
- Open source0
- Well designed0
- Flexibilty0
- Productive0
- Awesome0
- Expressive0
- Love it0
Pros of Tornado
- Open source37
- So fast31
- Great for microservices architecture27
- Websockets20
- Simple17
- Asynchronous14
- Python11
- Lightweight7
- Handles well persistent connexions3
Sign up to add or upvote prosMake informed product decisions
Cons of Flask
- Not JS10
- Context7
- Not fast5
- Don't has many module as in spring1
Cons of Tornado
- Event loop is complicated2
Sign up to add or upvote consMake informed product decisions
What is Flask?
What is Tornado?
Need advice about which tool to choose?Ask the StackShare community!
What companies use Tornado?
Sign up to get full access to all the companiesMake informed product decisions
Sign up to get full access to all the tool integrationsMake informed product decisions
Blog Posts
+17
+47+46+39+26