What is Flask and what are its top alternatives?
Top Alternatives to Flask
Django is a high-level Python Web framework that encourages rapid development and clean, pragmatic design. ...
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. ...
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 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. ...
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. ...
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 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
It is a powerful and flexible toolkit that makes it easy to build Web APIs.
Flask alternatives & related posts
- Rapid development603
- Open source447
- Great community388
- Easy to learn338
- Beautiful code202
- Great packages180
- Great libraries168
- Comes with auth and crud admin panel53
- Great documentation49
- Great for web47
- Great orm32
- Great for api28
- All included22
- Web Apps18
- Used by top startups14
- Easy setup11
- Convention over configuration8
- Allows for very rapid development with great libraries5
- The Django community5
- Its elegant and practical3
- Great MVC and templating engine3
- Easy to use2
- Easy to develop end to end AI Models2
- Fast prototyping2
- Full stack2
- Batteries included2
- Easy Structure , useful inbuilt library2
- Great peformance1
- Many libraries1
- Zero code burden to change databases1
- Have not found anything that it can't do1
- Very quick to get something up and running1
- Just the right level of abstraction1
- Python community1
- Full-Text Search1
- King of backend world1
- Underpowered templating24
- Underpowered ORM19
- Autoreload restarts whole server18
- URL dispatcher ignores HTTP method15
- Internal subcomponents coupling10
- Not nodejs7
- Configuration hell4
- Not as clean and nice documentation like Laravel3
- Bloated admin panel included2
- Not typed2
- Overwhelming folder structure2
- InEffective Multithreading1
related Django posts
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.
- Open source37
- So fast30
- Great for microservices architecture25
- Handles well persistent connexions3
- Event loop is complicated2
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.
- High performance183
- Robust routing147
- Open source66
- Great community51
- Hybrid web applications33
- Sinatra inspired8
- Well documented8
- Isomorphic js.. superfast and easy4
- Rapid development3
- Event loop2
- Socket connection2
- Resource available for learning2
- Light weight2
- Data stream1
- Not python21
- No multithreading14
- Not fast4
- Easily Insecure for Novices2
related ExpressJS posts
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:
- 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.
- Great libraries1.1K
- Open source789
- Great for apis477
- Great community414
- Great for realtime apps385
- Great for command line utilities290
- Node Modules77
- Uber Simple65
- Great modularity53
- Allows us to reuse code in the frontend53
- Easy to start38
- Great for Data Streaming33
- Non blocking IO23
- Can be used as a proxy16
- High performance, open source, scalable15
- Non-blocking and modular14
- Easy and Fun13
- Same lang as AngularJS12
- Easy and powerful11
- Future of BackEnd10
- Cross platform8
- Mean Stack6
- Easy concurrency5
- Great for webapps5
- Easy to use and fast and goes well with JSONdb's4
- Fast, simple code and async4
- Its amazingly fast and scalable3
- Isomorphic coolness3
- Great speed3
- Control everything3
- Fast development3
- One language, end-to-end2
- Scales, fast, simple, great community, npm, express2
- TypeScript Support2
- Easy to learn2
- Easy to use2
- It's fast2
- Less boilerplate code2
- Blazing fast2
- Not Python2
- Performant and fast prototyping2
- Sooper easy for the Backend connectivity2
- Great community2
- Event Driven0
- Bound to a single CPU46
- New framework every day37
- Lots of terrible examples on the internet33
- Asynchronous programming is the worst28
- Dependency based on GitHub11
- Dependency hell10
- Low computational power10
- Can block whole server easily7
- Callback functions may not fire on expected sequence6
- Very very Slow6
- Unneeded over complication3
- Breaking updates3
- No standard approach1
related Node.js posts
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.
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:
- Virtual dom645
- Data flow171
- Isn't an mvc framework121
- Reactive updates111
- Explicit app state109
- Learn once, write everywhere20
- Uni-directional data flow17
- Easy to Use16
- Works great with Flux Architecture14
- Great perfomance9
- Built by Facebook6
- Feels like the 90s4
- Easy to start3
- Server side views3
- TypeScript support2
- Great migration pathway for older systems2
- Fast evolving2
- Simple, easy to reason about and makes you productive2
- Fancy third party tools2
- Excellent Documentation2
- Scales super well2
- Just the View of MVC2
- Server Side Rendering2
- Rich ecosystem2
- Split your UI into components with one true state1
- Every decision architecture wise makes sense1
- Super easy1
- Beautiful and Neat Component Management1
- Has functional components1
- Very gentle learning curve1
- Strong Community1
- Has arrow functions1
- Allows creating single page applications1
- Start simple0
- Requires discipline to keep architecture organized31
- No predefined way to structure your app19
- Need to be familiar with lots of third party packages18
- Not enterprise friendly6
- State consistency with backend neglected1
- One-way binding only1
related React posts
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.
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.
- Great documentation2
- Super easy to use2
related Bottle posts
- Powerful and handy127
- Easy setup121
- Lots of "off the shelf" functionalities32
- Cloud Solid27
- Caches well21
- Many receipes around for obscure features19
- Integrations with most other Java frameworks17
- Spring ecosystem is great16
- Fast Performance With Microservices16
- Easy setup, Community Support, Solid for ERP apps11
- One-stop shop11
- Easy to parallelize10
- Easy setup, good for build erp systems, well documented9
- Easy setup, Git Integration8
- Powerful 3rd party libraries and frameworks8
- It's so easier to start a project on spring2
- Heavy weight18
- Annotation ceremony17
- Many config files needed10
- Excellent tools for cloud hosting, since 5.x4
related Spring Boot posts
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
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.
- Browsable api63
- Easy to use62
- Great documentation52
- Fast development41
- Easy to use, customizable, pluggable, serializer9
- Django ORM5
- Easy implementation2
- Less code2
- Bad documentation2
- Reimplements Django functionality2
- No support for URL Namespaces1
- Bad CSRF handling0
related Django REST framework posts
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
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.
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.