Alternatives to Flask logo

Alternatives to Flask

Django, Tornado, ExpressJS, Node.js, and React are the most popular alternatives and competitors to Flask.
12.1K
9.9K
+ 1
1.4K

What is Flask and what are its top alternatives?

Flask is intended for getting started very quickly and was developed with best intentions in mind.
Flask is a tool in the Microframeworks (Backend) category of a tech stack.
Flask is an open source tool with 54.1K GitHub stars and 14.1K GitHub forks. Here’s a link to Flask's open source repository on GitHub

Top Alternatives to Flask

  • Django

    Django

    Django is a high-level Python Web framework that encourages rapid development and clean, pragmatic design. ...

  • Tornado

    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. ...

  • ExpressJS

    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

    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

    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

    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. ...

  • Spring Boot

    Spring Boot

    Spring Boot makes it easy to create stand-alone, production-grade Spring based Applications that you can "just run". We take an opinionated view of the Spring platform and third-party libraries so you can get started with minimum fuss. Most Spring Boot applications need very little Spring configuration. ...

  • Django REST framework

    Django REST framework

    It is a powerful and flexible toolkit that makes it easy to build Web APIs.

Flask alternatives & related posts

Django logo

Django

21.9K
18.6K
3.5K
The Web framework for perfectionists with deadlines
21.9K
18.6K
+ 1
3.5K
PROS OF DJANGO
  • 603
    Rapid development
  • 447
    Open source
  • 388
    Great community
  • 338
    Easy to learn
  • 250
    Mvc
  • 203
    Elegant
  • 202
    Beautiful code
  • 181
    Free
  • 180
    Great packages
  • 168
    Great libraries
  • 56
    Restful
  • 53
    Comes with auth and crud admin panel
  • 52
    Powerful
  • 49
    Great documentation
  • 47
    Great for web
  • 37
    Python
  • 32
    Great orm
  • 28
    Great for api
  • 22
    All included
  • 18
    Web Apps
  • 16
    Fast
  • 14
    Used by top startups
  • 12
    Clean
  • 11
    Easy setup
  • 10
    Sexy
  • 8
    Convention over configuration
  • 5
    ORM
  • 5
    Allows for very rapid development with great libraries
  • 5
    The Django community
  • 3
    Mvt
  • 3
    Its elegant and practical
  • 3
    Great MVC and templating engine
  • 2
    Easy to use
  • 2
    Easy
  • 2
    Easy to develop end to end AI Models
  • 2
    Cross-Platform
  • 2
    Fast prototyping
  • 2
    Full stack
  • 2
    Batteries included
  • 2
    Easy Structure , useful inbuilt library
  • 1
    Great peformance
  • 1
    Many libraries
  • 1
    Zero code burden to change databases
  • 1
    Have not found anything that it can't do
  • 1
    Map
  • 1
    Scaffold
  • 1
    Modular
  • 1
    Very quick to get something up and running
  • 1
    Just the right level of abstraction
  • 1
    Python community
  • 1
    Full-Text Search
  • 1
    King of backend world
CONS OF DJANGO
  • 24
    Underpowered templating
  • 19
    Underpowered ORM
  • 18
    Autoreload restarts whole server
  • 15
    URL dispatcher ignores HTTP method
  • 10
    Internal subcomponents coupling
  • 7
    Not nodejs
  • 5
    Admin
  • 4
    Configuration hell
  • 3
    Not as clean and nice documentation like Laravel
  • 2
    Bloated admin panel included
  • 2
    Not typed
  • 2
    Python
  • 2
    Overwhelming folder structure
  • 1
    InEffective Multithreading

related Django posts

Dmitry Mukhin

Simple controls over complex technologies, as we put it, wouldn't be possible without neat UIs for our user areas including start page, dashboard, settings, and docs.

Initially, there was Django. Back in 2011, considering our Python-centric approach, that was the best choice. Later, we realized we needed to iterate on our website more quickly. And this led us to detaching Django from our front end. That was when we decided to build an SPA.

For building user interfaces, we're currently using React as it provided the fastest rendering back when we were building our toolkit. It’s worth mentioning Uploadcare is not a front-end-focused SPA: we aren’t running at high levels of complexity. If it were, we’d go with Ember.js.

However, there's a chance we will shift to the faster Preact, with its motto of using as little code as possible, and because it makes more use of browser APIs. One of our future tasks for our front end is to configure our Webpack bundler to split up the code for different site sections. For styles, we use PostCSS along with its plugins such as cssnano which minifies all the code.

All that allows us to provide a great user experience and quickly implement changes where they are needed with as little code as possible.

See more

Hey, so I developed a basic application with Python. But to use it, you need a python interpreter. I want to add a GUI to make it more appealing. What should I choose to develop a GUI? I have very basic skills in front end development (CSS, JavaScript). I am fluent in python. I'm looking for a tool that is easy to use and doesn't require too much code knowledge. I have recently tried out Flask, but it is kinda complicated. Should I stick with it, move to Django, or is there another nice framework to use?

See more
Tornado logo

Tornado

295
350
161
A Python web framework and asynchronous networking library, originally developed at FriendFeed
295
350
+ 1
161
PROS OF TORNADO
  • 37
    Open source
  • 30
    So fast
  • 25
    Great for microservices architecture
  • 20
    Websockets
  • 17
    Simple
  • 13
    Asynchronous
  • 9
    Python
  • 7
    Lightweight
  • 3
    Handles well persistent connexions
CONS OF TORNADO
  • 2
    Event loop is complicated

related Tornado posts

Around the time of their Series A, Pinterest’s stack included Python and Django, with Tornado and Node.js as web servers. Memcached / Membase and Redis handled caching, with RabbitMQ handling queueing. Nginx, HAproxy and Varnish managed static-delivery and load-balancing, with persistent data storage handled by MySQL.

See more
ExpressJS logo

ExpressJS

16.6K
12.5K
1.5K
Sinatra inspired web development framework for node.js -- insanely fast, flexible, and simple
16.6K
12.5K
+ 1
1.5K
PROS OF EXPRESSJS
  • 362
    Simple
  • 319
    Node.js
  • 234
    Javascript
  • 183
    High performance
  • 147
    Robust routing
  • 66
    Open source
  • 63
    Middlewares
  • 51
    Great community
  • 33
    Hybrid web applications
  • 8
    Sinatra inspired
  • 8
    Well documented
  • 4
    Isomorphic js.. superfast and easy
  • 3
    Rapid development
  • 2
    Event loop
  • 2
    Socket connection
  • 2
    Npm
  • 2
    Resource available for learning
  • 2
    Light weight
  • 1
    Data stream
  • 1
    Callbacks
  • 0
    Xxx
CONS OF EXPRESSJS
  • 21
    Not python
  • 15
    Overrated
  • 14
    No multithreading
  • 6
    Javascript
  • 4
    Not fast
  • 2
    Easily Insecure for Novices

related ExpressJS posts

Simon Reymann
Senior Fullstack Developer at QUANTUSflow Software GmbH · | 23 upvotes · 1.5M views

Our whole Node.js backend stack consists of the following tools:

  • Lerna as a tool for multi package and multi repository management
  • npm as package manager
  • NestJS as Node.js framework
  • TypeScript as programming language
  • ExpressJS as web server
  • Swagger UI for visualizing and interacting with the API’s resources
  • Postman as a tool for API development
  • TypeORM as object relational mapping layer
  • JSON Web Token for access token management

The main reason we have chosen Node.js over PHP is related to the following artifacts:

  • Made for the web and widely in use: Node.js is a software platform for developing server-side network services. Well-known projects that rely on Node.js include the blogging software Ghost, the project management tool Trello and the operating system WebOS. Node.js requires the JavaScript runtime environment V8, which was specially developed by Google for the popular Chrome browser. This guarantees a very resource-saving architecture, which qualifies Node.js especially for the operation of a web server. Ryan Dahl, the developer of Node.js, released the first stable version on May 27, 2009. He developed Node.js out of dissatisfaction with the possibilities that JavaScript offered at the time. The basic functionality of Node.js has been mapped with JavaScript since the first version, which can be expanded with a large number of different modules. The current package managers (npm or Yarn) for Node.js know more than 1,000,000 of these modules.
  • Fast server-side solutions: Node.js adopts the JavaScript "event-loop" to create non-blocking I/O applications that conveniently serve simultaneous events. With the standard available asynchronous processing within JavaScript/TypeScript, highly scalable, server-side solutions can be realized. The efficient use of the CPU and the RAM is maximized and more simultaneous requests can be processed than with conventional multi-thread servers.
  • A language along the entire stack: Widely used frameworks such as React or AngularJS or Vue.js, which we prefer, are written in JavaScript/TypeScript. If Node.js is now used on the server side, you can use all the advantages of a uniform script language throughout the entire application development. The same language in the back- and frontend simplifies the maintenance of the application and also the coordination within the development team.
  • Flexibility: Node.js sets very few strict dependencies, rules and guidelines and thus grants a high degree of flexibility in application development. There are no strict conventions so that the appropriate architecture, design structures, modules and features can be freely selected for the development.
See more

Hello, I hope everyone is doing good and safe. I need advice on what to learn more, I have started learning HTML, CSS, Bootstrap, JavaScript, Node.js, ExpressJS, React. eventually will learn MongoDB too. I would like to be a Front End developer or full-stack developer. What else would be the suggestion to get a job and what things I need to focus more on as a fresher to make my skills better. Do I have to be good in Algorithms and Dynamic Programming to find a job for entry-level? Looking forward to hearing from you guys for suggestions. 

See more
Node.js logo

Node.js

98.8K
78.7K
8.3K
A platform built on Chrome's JavaScript runtime for easily building fast, scalable network applications
98.8K
78.7K
+ 1
8.3K
PROS OF NODE.JS
  • 1.4K
    Npm
  • 1.3K
    Javascript
  • 1.1K
    Great libraries
  • 1K
    High-performance
  • 789
    Open source
  • 477
    Great for apis
  • 467
    Asynchronous
  • 414
    Great community
  • 385
    Great for realtime apps
  • 290
    Great for command line utilities
  • 77
    Node Modules
  • 75
    Websockets
  • 65
    Uber Simple
  • 53
    Great modularity
  • 53
    Allows us to reuse code in the frontend
  • 38
    Easy to start
  • 33
    Great for Data Streaming
  • 29
    Realtime
  • 25
    Awesome
  • 23
    Non blocking IO
  • 16
    Can be used as a proxy
  • 15
    High performance, open source, scalable
  • 14
    Non-blocking and modular
  • 13
    Easy and Fun
  • 12
    Same lang as AngularJS
  • 11
    Easy and powerful
  • 10
    Future of BackEnd
  • 9
    Fast
  • 8
    Cross platform
  • 8
    Scalability
  • 6
    Mean Stack
  • 6
    Fullstack
  • 6
    Simple
  • 5
    Easy concurrency
  • 5
    Great for webapps
  • 4
    Easy to use and fast and goes well with JSONdb's
  • 4
    Friendly
  • 4
    React
  • 4
    Fast, simple code and async
  • 4
    Typescript
  • 3
    Its amazingly fast and scalable
  • 3
    Isomorphic coolness
  • 3
    Great speed
  • 3
    Scalable
  • 3
    Control everything
  • 3
    Fast development
  • 2
    One language, end-to-end
  • 2
    Scales, fast, simple, great community, npm, express
  • 2
    TypeScript Support
  • 2
    Easy to learn
  • 2
    Easy to use
  • 2
    It's fast
  • 2
    Less boilerplate code
  • 2
    Blazing fast
  • 2
    Not Python
  • 2
    Performant and fast prototyping
  • 2
    Sooper easy for the Backend connectivity
  • 2
    Great community
  • 1
    Easy
  • 1
    Lovely
  • 0
    Event Driven
  • 0
    Javascript2
CONS OF NODE.JS
  • 46
    Bound to a single CPU
  • 37
    New framework every day
  • 33
    Lots of terrible examples on the internet
  • 28
    Asynchronous programming is the worst
  • 22
    Callback
  • 16
    Javascript
  • 11
    Dependency based on GitHub
  • 10
    Dependency hell
  • 10
    Low computational power
  • 7
    Can block whole server easily
  • 6
    Callback functions may not fire on expected sequence
  • 6
    Very very Slow
  • 3
    Unneeded over complication
  • 3
    Breaking updates
  • 3
    Unstable
  • 1
    No standard approach

related Node.js posts

Nick Rockwell
SVP, Engineering at Fastly · | 42 upvotes · 1.4M views

When I joined NYT there was already broad dissatisfaction with the LAMP (Linux Apache HTTP Server MySQL PHP) Stack and the front end framework, in particular. So, I wasn't passing judgment on it. I mean, LAMP's fine, you can do good work in LAMP. It's a little dated at this point, but it's not ... I didn't want to rip it out for its own sake, but everyone else was like, "We don't like this, it's really inflexible." And I remember from being outside the company when that was called MIT FIVE when it had launched. And been observing it from the outside, and I was like, you guys took so long to do that and you did it so carefully, and yet you're not happy with your decisions. Why is that? That was more the impetus. If we're going to do this again, how are we going to do it in a way that we're gonna get a better result?

So we're moving quickly away from LAMP, I would say. So, right now, the new front end is React based and using Apollo. And we've been in a long, protracted, gradual rollout of the core experiences.

React is now talking to GraphQL as a primary API. There's a Node.js back end, to the front end, which is mainly for server-side rendering, as well.

Behind there, the main repository for the GraphQL server is a big table repository, that we call Bodega because it's a convenience store. And that reads off of a Kafka pipeline.

See more
Conor Myhrvold
Tech Brand Mgr, Office of CTO at Uber · | 37 upvotes · 3.5M views

How Uber developed the open source, end-to-end distributed tracing Jaeger , now a CNCF project:

Distributed tracing is quickly becoming a must-have component in the tools that organizations use to monitor their complex, microservice-based architectures. At Uber, our open source distributed tracing system Jaeger saw large-scale internal adoption throughout 2016, integrated into hundreds of microservices and now recording thousands of traces every second.

Here is the story of how we got here, from investigating off-the-shelf solutions like Zipkin, to why we switched from pull to push architecture, and how distributed tracing will continue to evolve:

https://eng.uber.com/distributed-tracing/

(GitHub Pages : https://www.jaegertracing.io/, GitHub: https://github.com/jaegertracing/jaeger)

Bindings/Operator: Python Java Node.js Go C++ Kubernetes JavaScript OpenShift C# Apache Spark

See more
React logo

React

89.1K
68.3K
3.7K
A JavaScript library for building user interfaces
89.1K
68.3K
+ 1
3.7K
PROS OF REACT
  • 737
    Components
  • 645
    Virtual dom
  • 552
    Performance
  • 477
    Simplicity
  • 433
    Composable
  • 171
    Data flow
  • 156
    Declarative
  • 121
    Isn't an mvc framework
  • 111
    Reactive updates
  • 109
    Explicit app state
  • 28
    JSX
  • 20
    Learn once, write everywhere
  • 17
    Uni-directional data flow
  • 16
    Easy to Use
  • 14
    Works great with Flux Architecture
  • 9
    Great perfomance
  • 6
    Built by Facebook
  • 4
    Feels like the 90s
  • 4
    Speed
  • 4
    Scalable
  • 3
    Functional
  • 3
    Javascript
  • 3
    Easy to start
  • 3
    Server side views
  • 2
    TypeScript support
  • 2
    Great migration pathway for older systems
  • 2
    SSR
  • 2
    Fast evolving
  • 2
    Simple, easy to reason about and makes you productive
  • 2
    Fancy third party tools
  • 2
    Excellent Documentation
  • 2
    Scales super well
  • 2
    Just the View of MVC
  • 2
    Server Side Rendering
  • 2
    Awesome
  • 2
    Cross-platform
  • 2
    Hooks
  • 2
    Rich ecosystem
  • 1
    Split your UI into components with one true state
  • 1
    Props
  • 1
    Fragments
  • 1
    Sharable
  • 1
    Every decision architecture wise makes sense
  • 1
    Permissively-licensed
  • 1
    Super easy
  • 1
    Beautiful and Neat Component Management
  • 1
    Has functional components
  • 1
    Very gentle learning curve
  • 1
    Closer to standard JavaScript and HTML than others
  • 1
    Sdfsdfsdf
  • 1
    Strong Community
  • 1
    Has arrow functions
  • 1
    Allows creating single page applications
  • 1
    Simple
  • 0
    Start simple
CONS OF REACT
  • 31
    Requires discipline to keep architecture organized
  • 19
    No predefined way to structure your app
  • 18
    Need to be familiar with lots of third party packages
  • 6
    JSX
  • 6
    Not enterprise friendly
  • 1
    State consistency with backend neglected
  • 1
    One-way binding only

related React posts

Vaibhav Taunk
Team Lead at Technovert · | 31 upvotes · 1.3M views

I am starting to become a full-stack developer, by choosing and learning .NET Core for API Development, Angular CLI / React for UI Development, MongoDB for database, as it a NoSQL DB and Flutter / React Native for Mobile App Development. Using Postman, Markdown and Visual Studio Code for development.

See more
Johnny Bell
Software Engineer at Weedmaps · | 26 upvotes · 284.6K views
Shared insights
on
Vue.jsVue.jsReactReact

I've used both Vue.js and React and I would stick with React. I know that Vue.js seems easier to write and its much faster to pick up however as you mentioned above React has way more ready made components you can just plugin, and the community for React is very big.

It might be a bit more of a steep learning curve for your friend to learn React over Vue.js but I think in the long run its the better option.

See more
Bottle logo

Bottle

37
43
5
A lightweight WSGI micro web-framework for Python
37
43
+ 1
5
PROS OF BOTTLE
  • 2
    Great documentation
  • 2
    Super easy to use
  • 1
    Faster
CONS OF BOTTLE
    Be the first to leave a con

    related Bottle posts

    Spring Boot logo

    Spring Boot

    13.8K
    11.7K
    841
    Create Spring-powered, production-grade applications and services with absolute minimum fuss
    13.8K
    11.7K
    + 1
    841
    PROS OF SPRING BOOT
    • 127
      Powerful and handy
    • 121
      Easy setup
    • 111
      Java
    • 83
      Spring
    • 79
      Fast
    • 39
      Extensible
    • 32
      Lots of "off the shelf" functionalities
    • 27
      Cloud Solid
    • 21
      Caches well
    • 19
      Many receipes around for obscure features
    • 18
      Modular
    • 18
      Productive
    • 17
      Integrations with most other Java frameworks
    • 16
      Spring ecosystem is great
    • 16
      Fast Performance With Microservices
    • 14
      Community
    • 13
      Auto-configuration
    • 11
      Easy setup, Community Support, Solid for ERP apps
    • 11
      One-stop shop
    • 10
      Easy to parallelize
    • 9
      Cross-platform
    • 9
      Easy setup, good for build erp systems, well documented
    • 8
      Easy setup, Git Integration
    • 8
      Powerful 3rd party libraries and frameworks
    • 2
      Kotlin
    • 2
      It's so easier to start a project on spring
    CONS OF SPRING BOOT
    • 18
      Heavy weight
    • 17
      Annotation ceremony
    • 10
      Many config files needed
    • 7
      Java
    • 5
      Reactive
    • 4
      Excellent tools for cloud hosting, since 5.x

    related Spring Boot posts

    Praveen Mooli
    Engineering Manager at Taylor and Francis · | 14 upvotes · 1.6M views

    We are in the process of building a modern content platform to deliver our content through various channels. We decided to go with Microservices architecture as we wanted scale. Microservice architecture style is an approach to developing an application as a suite of small independently deployable services built around specific business capabilities. You can gain modularity, extensive parallelism and cost-effective scaling by deploying services across many distributed servers. Microservices modularity facilitates independent updates/deployments, and helps to avoid single point of failure, which can help prevent large-scale outages. We also decided to use Event Driven Architecture pattern which is a popular distributed asynchronous architecture pattern used to produce highly scalable applications. The event-driven architecture is made up of highly decoupled, single-purpose event processing components that asynchronously receive and process events.

    To build our #Backend capabilities we decided to use the following: 1. #Microservices - Java with Spring Boot , Node.js with ExpressJS and Python with Flask 2. #Eventsourcingframework - Amazon Kinesis , Amazon Kinesis Firehose , Amazon SNS , Amazon SQS, AWS Lambda 3. #Data - Amazon RDS , Amazon DynamoDB , Amazon S3 , MongoDB Atlas

    To build #Webapps we decided to use Angular 2 with RxJS

    #Devops - GitHub , Travis CI , Terraform , Docker , Serverless

    See more

    Is learning Spring and Spring Boot for web apps back-end development is still relevant in 2021? Feel free to share your views with comparison to Django/Node.js/ ExpressJS or other frameworks.

    Please share some good beginner resources to start learning about spring/spring boot framework to build the web apps.

    See more
    Django REST framework logo

    Django REST framework

    1.4K
    1.4K
    297
    Web APIs for Django
    1.4K
    1.4K
    + 1
    297
    PROS OF DJANGO REST FRAMEWORK
    • 63
      Browsable api
    • 62
      Easy to use
    • 52
      Great documentation
    • 49
      Customizable
    • 41
      Fast development
    • 9
      Easy to use, customizable, pluggable, serializer
    • 8
      Python
    • 5
      Django ORM
    • 4
      FastSerialize
    • 2
      Easy implementation
    • 2
      Less code
    • 0
      Dsasda
    CONS OF DJANGO REST FRAMEWORK
    • 2
      Bad documentation
    • 2
      Reimplements Django functionality
    • 1
      No support for URL Namespaces
    • 0
      Bad CSRF handling

    related Django REST framework posts

    Tim Abbott

    Zulip has been powered by Django since the very early days of its development with Django 1.4, back in 2012. As a reasonably mature web application with significant scale, we're at the stage in many companies' development where one starts to rip out more and more of the web framework to optimize things or just make them work the way we want. (E.g. while I was at Dropbox in early 2016, we discovered we only had about 600 lines of code left from the original Pylons framework that actually ran).

    One of the things that has been really fantastic about Django is that we're still happily using it for the vast majority of code in the project, and every time Django comes out with a new release, I read the changelog and get excited about several improvements that actually make my life better. While Django has made some design decisions that I don't agree with (e.g. I'm not a fan of Django REST framework, and think it makes life more difficult), Django also makes it easy to do your own thing, which we've done to great effect (see the linked article for details on our has_request_variables framework).

    Overall I think we've gotten a ton of value out of Python and Django and would recommend it to anyone starting a new full-featured web application project today.

    See more

    Hi

    I’ve been using Django for the last year on and off to do my backend API. I’m getting a bit frustrated with the Django REST framework with the setup of the serializers and Django for the lack of web sockets. I’m considering either Spring or .NET Core. I’m familiar with Kotlin and C# but I’ve not built any substantial projects with them. I like OOP, building a desktop app, web API, and also the potential to get a job in the future or building a tool at work to manage my documents, dashboard and processes point cloud data.

    I’m familiar with c/cpp, TypeScript.

    I would love your insights on where I should go.

    See more