APIs Case Study Development Web Web Servers and MicroFWs (Flask/Tornado/Nginx/...)See in schedule
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!
Type: Talk (45 mins); Python level: Intermediate; Domain level: Intermediate
Long-time pythonista, Django fan, co-maintainer and co-author of DRF-Schema-Adapter.
Recently interested by Python running on different hardware.
I am from Belgium and have been involved in open-source at different levels for a bit more than a decade now.
One of the things I enjoy the most is sharing knowledge with others. And this is why I enjoy writing tutorials as well as giving talks and workshops.