Flask vs Spring Boot: What are the differences?
Developers describe Flask as "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. On the other hand, Spring Boot is detailed as "Create Spring-powered, production-grade applications and services with absolute minimum fuss". 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.
Flask can be classified as a tool in the "Microframeworks (Backend)" category, while Spring Boot is grouped under "Frameworks (Full Stack)".
"Lightweight", "Python" and "Minimal" are the key factors why developers consider Flask; whereas "Powerful and handy", "Easy setup" and "Java" are the primary reasons why Spring Boot is favored.
Flask and Spring Boot are both open source tools. Flask with 45.2K GitHub stars and 12.7K forks on GitHub appears to be more popular than Spring Boot with 39.8K GitHub stars and 25.8K GitHub forks.
According to the StackShare community, Flask has a broader approval, being mentioned in 511 company stacks & 531 developers stacks; compared to Spring Boot, which is listed in 333 company stacks and 615 developer stacks.
What is Flask?
What is Spring Boot?
Need advice about which tool to choose?Ask the StackShare community!
Sign up to add, upvote and see more prosMake informed product decisions
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
Unlike our frontend, we chose Flask, a microframework, for our backend. We use it with Python 3 and Gunicorn.
One of the reasons was that I have significant experience with this framework. However, it also was a rather straightforward choice given that our backend almost only serves REST APIs, and that most of the work is talking to the database with SQLAlchemy .
We could have gone with something like Hug but it is kind of early. We might revisit that decision for new services later on.
I use Spring-Boot because it almost let you get things done quickly for a JVM-target project, with auto configuration components and dependency management starters. It is almost perfectly tailored for microservices applications development with a single unit deployment artifact (JAR) along with support for Service Registry and Discovery, Circuit Breaker pattern...
Any third-party library or any back-end service would perfectly integrate well since Spring offers integration support for most of mainstream services, let it be a RDBMS service, a NoSQL database, a Message Broker...
Coming to day-to-day development, Spring-Boot enjoys a great community so you can get support, direction, focused guidance from almost everywhere.
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
Flask is a light, yet powerful Python web framework perfect for quickly building smaller web applications. It's a "micro-framework" that's easy to learn and simple to use, so it's perfect for those new to web development as well as those looking to rapidly develop a web application.
spring boot allow my team to start building web services quickly and package it in a stand alone application
I use Flask for times when I need to create a REST API that interfaces with other Python code, or there is no specific reason why I'd want to use Node.JS. I prefer Flask because of its small learning curve, allowing me to get started coding as quickly as possible
This lightweight web framework enables quick REST API development while enabling easy clustering, and the usage of multiple worker processes required to scale the REST API service to meet high volume requirements.
Spring-Boot allows us to create stand-alone web servers and helps us configure many of our dependencies with sane default, while maintaining flexibility where we need it.
Service to query NOAA weather forecasts data and service to build tidal current forecast maps using AWS EC2 and Geoserver
Flask drives our APIs, both the Website APIs and the majority of the REST Messaging APIs