Flask vs Polymer: 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, Polymer is detailed as "A new library built on top of Web Components, designed to leverage the evolving web platform on modern browsers". Polymer is a new type of library for the web, designed to leverage the existing browser infrastructure to provide the encapsulation and extendability currently only available in JS libraries. Polymer is based on a set of future technologies, including Shadow DOM, Custom Elements and Model Driven Views. Currently these technologies are implemented as polyfills or shims, but as browsers adopt these features natively, the platform code that drives Polymer evacipates, leaving only the value-adds.
Flask can be classified as a tool in the "Microframeworks (Backend)" category, while Polymer is grouped under "Front-End Frameworks".
"Lightweight" is the top reason why over 261 developers like Flask, while over 49 developers mention "Web components" as the leading cause for choosing Polymer.
Flask and Polymer are both open source tools. It seems that Flask with 45.2K GitHub stars and 12.7K forks on GitHub has more adoption than Polymer with 21.1K GitHub stars and 2K GitHub forks.
Netflix, reddit, and Lyft are some of the popular companies that use Flask, whereas Polymer is used by Telemetry, AX Semantics, and USERcycle. Flask has a broader approval, being mentioned in 511 company stacks & 531 developers stacks; compared to Polymer, which is listed in 42 company stacks and 32 developer stacks.
What is Flask?
What is Polymer?
Need advice about which tool to choose?Ask the StackShare community!
Sign up to add, upvote and see more prosMake informed product decisions
What are the cons of using Polymer?
Sign up to get full access to all the companiesMake informed product decisions
What tools integrate with Polymer?
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.
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.
In process of Learning Technics- Studing to know more. I was introduced in a Google event.
Polymer is another Google offering that focuses on Web Components, an up-and-coming collection of technologies that provide web developers with the ability to create customer HTML elements.
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
Polymer is super future-focused and really great to build in. The biggest plus for us is how its component-focused approach keeps things modular and maintainable. It also makes it really easy to implement material design.
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.
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