We're sorry but this page doesn't work properly without JavaScript enabled. Please enable it to continue.
Feedback

Writing a python web framework in 2021

Formal Metadata

Title
Writing a python web framework in 2021
Title of Series
Number of Parts
115
Author
Contributors
License
CC Attribution - NonCommercial - ShareAlike 4.0 International:
You are free to use, adapt and copy, distribute and transmit the work or content in adapted or unchanged form for any legal and non-commercial purpose as long as the work is attributed to the author in the manner specified by the author or licensor and the work or content is shared also in adapted form only under the conditions of this
Identifiers
Publisher
Release Date
Language

Content Metadata

Subject Area
Genre
Abstract
Django, Flask and Pyramid are among the most popular Python web frameworks and for good reasons. But... Those projects are over 10 years old and tied to decisions made at the time of the first commit. The fact the web was a server-rendered world of request/response cycle is a big part in those decisions. Today's web has shifted with a special attention to API's and websockets. It still needs to care for the "regular" server-rendered page but it is not its only focus anymore! Not only that, but (well-documented) tools are available today that were not there 10 years ago. So, if you wanted to write the next big webframefork in 2021, what tools and libraries would be at your disposal? Somewhat ironically, those 3 main frameworks I mentioned have given rise to, or at least inspired some, "derivate" standalone libraries like ORM's, or schema serializers that can be used by a third party framework. Other libraries have also spawned as ports from other languages and, finally, the python WSGI ecosystem (like middlewares) has also grown in that time frame. So, is writing a python web framework in 2021 mostly a matter of picking up existing tools and putting them together? Let's take a closer look!