Flask vs Play

Overview

Flask

Stacks19.3K

Followers16.2K

Votes60

Play

Stacks752

Followers609

Votes496

GitHub Stars12.6K

Forks4.1K

Flask vs Play: What are the differences?

<Write Introduction here>

Routing Mechanism: Flask uses decorator routing in Python for mapping URLs to functions, while Play framework uses a built-in routing DSL (Domain Specific Language) that allows defining routes in a route file using a specific syntax.
Language Support: Flask is designed to work with Python, whereas Play framework supports multiple languages like Java and Scala, providing developers with flexibility to choose the language of their choice for development.
Template Engine: Flask uses Jinja2 as its default template engine, offering features like template inheritance and autoescaping, while Play framework includes Twirl, a type-safe template engine that integrates seamlessly with Scala code.
Asynchronous Programming: Flask is not asynchronous by default, but libraries like Flask-SocketIO can be added to enable asynchronous communication, whereas Play framework natively supports asynchronous programming, allowing developers to build highly scalable and responsive applications.
Database Access: Flask supports various database libraries like SQLAlchemy for ORM (Object Relational Mapping) or plain SQL, making it flexible for database access, whereas Play framework has built-in support for Slick, a functional relational mapping library that integrates well with Scala code.
Development Environment: Flask is more lightweight and suitable for smaller projects or microservices, offering a quick setup and easy development process, while Play framework provides a full-fledged development environment with features like hot reloading, built-in testing, and dependency injection for larger and complex applications.

In Summary, the key differences between Flask and Play framework lie in their routing mechanism, language support, template engines, asynchronous programming capabilities, database access options, and development environments, catering to different developer preferences and project requirements.

Share your Stack

Help developers discover the tools you use. Get visibility for your team's tech choices and contribute to the community's knowledge.

View Docs

CLI (Node.js)

Manual

Advice on Flask, Play

Kristan Eres

Senior Solutions Analyst

Jul 30, 2020

Needs adviceon

Django

Python

Flask

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?

392k views392k

Comments

Saurav

Application Devloper at Bny Mellon

Mar 27, 2020

Needs advice

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.

337k views337k

Comments

Girish

Software Engineer at FireVisor Systems

Apr 17, 2020

Needs adviceon

Python

Nameko

RabbitMQ

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.

310k views310k

Comments

Detailed Comparison

Flask	Play
Flask is intended for getting started very quickly and was developed with best intentions in mind.	Play Framework makes it easy to build web applications with Java & Scala. Play is based on a lightweight, stateless, web-friendly architecture. Built on Akka, Play provides predictable and minimal resource consumption (CPU, memory, threads) for highly-scalable applications.
Statistics
GitHub Stars -	GitHub Stars 12.6K
GitHub Forks -	GitHub Forks 4.1K
Stacks 19.3K	Stacks 752
Followers 16.2K	Followers 609
Votes 60	Votes 496
Pros & Cons
Pros 10 For it flexibility 9 Flexibilty and easy to use 7 User friendly 6 Secured 5 Unopinionated Cons 10 Not JS 7 Context 5 Not fast 1 Don't has many module as in spring	Pros 81 Scala 55 Built on akka 55 Web-friendly architecture 50 Stateless 47 High-scalable Cons 3 Evolves fast, keep up with releases 1 Unnecessarily complicated

What are some alternatives to Flask, Play?

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.

Rails

Rails is a web-application framework that includes everything needed to create database-backed web applications according to the Model-View-Controller (MVC) pattern.

Django

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

Laravel

It is a web application framework with expressive, elegant syntax. It attempts to take the pain out of development by easing common tasks used in the majority of web projects, such as authentication, routing, sessions, and caching.

.NET

.NET is a general purpose development platform. With .NET, you can use multiple languages, editors, and libraries to build native applications for web, mobile, desktop, gaming, and IoT for Windows, macOS, Linux, Android, and more.

ASP.NET Core

A free and open-source web framework, and higher performance than ASP.NET, developed by Microsoft and the community. It is a modular framework that runs on both the full .NET Framework, on Windows, and the cross-platform .NET Core.

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.

Symfony

It is written with speed and flexibility in mind. It allows developers to build better and easy to maintain websites with PHP..

Spring

A key element of Spring is infrastructural support at the application level: Spring focuses on the "plumbing" of enterprise applications so that teams can focus on application-level business logic, without unnecessary ties to specific deployment environments.

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.

Related Comparisons

Flask vs Play: What are the differences?

<Write Introduction here>

Routing Mechanism: Flask uses decorator routing in Python for mapping URLs to functions, while Play framework uses a built-in routing DSL (Domain Specific Language) that allows defining routes in a route file using a specific syntax.
Language Support: Flask is designed to work with Python, whereas Play framework supports multiple languages like Java and Scala, providing developers with flexibility to choose the language of their choice for development.
Template Engine: Flask uses Jinja2 as its default template engine, offering features like template inheritance and autoescaping, while Play framework includes Twirl, a type-safe template engine that integrates seamlessly with Scala code.
Asynchronous Programming: Flask is not asynchronous by default, but libraries like Flask-SocketIO can be added to enable asynchronous communication, whereas Play framework natively supports asynchronous programming, allowing developers to build highly scalable and responsive applications.
Database Access: Flask supports various database libraries like SQLAlchemy for ORM (Object Relational Mapping) or plain SQL, making it flexible for database access, whereas Play framework has built-in support for Slick, a functional relational mapping library that integrates well with Scala code.
Development Environment: Flask is more lightweight and suitable for smaller projects or microservices, offering a quick setup and easy development process, while Play framework provides a full-fledged development environment with features like hot reloading, built-in testing, and dependency injection for larger and complex applications.

Flask vs Play

Overview