Need advice about which tool to choose?Ask the StackShare community!

Flask

16.7K
14.2K
+ 1
1.6K
Tornado

378
387
+ 1
165
Add tool

Flask vs Tornado: What are the differences?

What is Flask? a microframework for Python based on Werkzeug, Jinja 2 and good intentions. Flask is intended for getting started very quickly and was developed with best intentions in mind.

What is Tornado? A Python web framework and asynchronous networking library, originally developed at FriendFeed. By using non-blocking network I/O, Tornado can scale to tens of thousands of open connections, making it ideal for long polling, WebSockets, and other applications that require a long-lived connection to each user.

Flask belongs to "Microframeworks (Backend)" category of the tech stack, while Tornado can be primarily classified under "Frameworks (Full Stack)".

"Lightweight" is the top reason why over 261 developers like Flask, while over 34 developers mention "Open source" as the leading cause for choosing Tornado.

Flask and Tornado are both open source tools. It seems that Flask with 44.8K GitHub stars and 12.6K forks on GitHub has more adoption than Tornado with 17.9K GitHub stars and 4.97K GitHub forks.

reddit, Lyft, and MIT are some of the popular companies that use Flask, whereas Tornado is used by Keen, Lensley, and dotCloud. Flask has a broader approval, being mentioned in 502 company stacks & 509 developers stacks; compared to Tornado, which is listed in 69 company stacks and 16 developer stacks.

Advice on Flask and Tornado
kristan-dev
Senior Solutions Analyst · | 8 upvotes · 244.6K views

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?

See more
Replies (1)
Rafael Torres
Technical Lead at 4Agile · | 9 upvotes · 235.2K views

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.

See more
Girish Sharma
Software Engineer at FireVisor Systems · | 6 upvotes · 192.5K views
Needs advice
on
BottleBottleFlaskFlask
and
NamekoNameko

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.

See more
Replies (1)
Recommends
BottleBottle

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.

See more
Saurav Pandit
Application Devloper at Bny Mellon · | 5 upvotes · 197.7K views

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.

See more
Replies (1)
Recommends
FlaskFlask
at

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.

See more
Needs advice
on
FlaskFlask
and
TornadoTornado

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

See more
Replies (4)
Srikanth Gopalakrishnan
WIreless Security Intern at Aruba Networks · | 3 upvotes · 5.6K views
Recommends
FlaskFlask

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.

See more
Jelena Dedovic
Recommends
BottleBottle

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.

See more
Gergely Polonkai
Lead developer at Benchmarked.games · | 2 upvotes · 5.5K views
Recommends
FlaskFlask

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.

See more
SeungWon Jeong
Recommends
FlaskFlask

Speed: tornado Large community & documentation + easy: flask

See more
Get Advice from developers at your company using StackShare Enterprise. Sign up for StackShare Enterprise.
Learn More
Pros of Flask
Pros of Tornado
  • 318
    Lightweight
  • 274
    Python
  • 216
    Minimal
  • 148
    Open source
  • 100
    Documentation
  • 68
    Easy to use
  • 55
    Easy to setup and get it going
  • 54
    Well designed
  • 50
    Easy to develop and maintain applications
  • 47
    Easy to get started
  • 21
    Beautiful code
  • 19
    Rapid development
  • 16
    Powerful
  • 15
    Expressive
  • 14
    Flexibilty
  • 13
    Get started quickly
  • 13
    Awesome
  • 13
    Simple to use
  • 13
    Customizable
  • 12
    Speed
  • 12
    Love it
  • 11
    Easy to integrate
  • 10
    Perfect for small to large projects with superb docs.
  • 10
    For it flexibility
  • 9
    Productive
  • 9
    Flexibilty and easy to use
  • 8
    Flask
  • 8
    Not JS
  • 7
    User friendly
  • 6
    Secured
  • 5
    Unopinionated
  • 3
    Orm
  • 2
    Secure
  • 37
    Open source
  • 31
    So fast
  • 27
    Great for microservices architecture
  • 20
    Websockets
  • 17
    Simple
  • 13
    Asynchronous
  • 10
    Python
  • 7
    Lightweight
  • 3
    Handles well persistent connexions

Sign up to add or upvote prosMake informed product decisions

Cons of Flask
Cons of Tornado
  • 10
    Not JS
  • 7
    Context
  • 5
    Not fast
  • 1
    Don't has many module as in spring
  • 2
    Event loop is complicated

Sign up to add or upvote consMake informed product decisions

- No public GitHub repository available -

What is Flask?

Flask is intended for getting started very quickly and was developed with best intentions in mind.

What is Tornado?

By using non-blocking network I/O, Tornado can scale to tens of thousands of open connections, making it ideal for long polling, WebSockets, and other applications that require a long-lived connection to each user.

Need advice about which tool to choose?Ask the StackShare community!

What companies use Flask?
What companies use Tornado?
See which teams inside your own company are using Flask or Tornado.
Sign up for StackShare EnterpriseLearn More

Sign up to get full access to all the companiesMake informed product decisions

What tools integrate with Flask?
What tools integrate with Tornado?

Sign up to get full access to all the tool integrationsMake informed product decisions

Blog Posts

What are some alternatives to Flask and Tornado?
Django
Django is a high-level Python Web framework that encourages rapid development and clean, pragmatic design.
ExpressJS
Express is a minimal and flexible node.js web application framework, providing a robust set of features for building single and multi-page, and hybrid web applications.
Node.js
Node.js uses an event-driven, non-blocking I/O model that makes it lightweight and efficient, perfect for data-intensive real-time applications that run across distributed devices.
React
Lots of people use React as the V in MVC. Since React makes no assumptions about the rest of your technology stack, it's easy to try it out on a small feature in an existing project.
Bottle
It is distributed as a single file module and has no dependencies other than the Python Standard Library. It has fast and pythonic built-in template engine and support for mako, jinja2 and cheetah templates.
See all alternatives