Making the wrong choice in the Python web framework is very difficult, Pyramid's introduction page /introduction.html#what-makes-pyramid-unique). As a result of my research, I came to the conclusion that this is exactly the case. When I personally built a website in December 2015, I was at a loss as to which web framework to build. This article is a memorandum for consideration at that time.
Speed comparison with everyone's favorite TechEmpower Web Framework Benchmarks. At that point, django, which was seriously profound, was out of consideration because I wanted to reduce server costs and operating costs anyway. The bottle is still fast.
I summarized it in the Yes / No chart. Session is not required because the login function is not built. I decided to build it with Flask, which is simple, has low learning cost, and operates at high speed.
Information that was considered but did not contribute to the selection. Making the wrong choice in Python's web framework is still difficult
All frameworks work with 3 systems.
Python + nginx + uWsgi + WebFramework, any framework works. Considering only the speed, it seems that Tornado should be used for the Web server. (Unverified)
Web framework | O/R mapper |
---|---|
Django | Original ORM |
Pyramid | SQLAlchemy |
Flask | Supports SQLAlchemy |
Choosing a Web Framework: Django, Flask, or Pyramid Let's use the convenient and super powerful WSGI server uWSGI Add Star
Recommended Posts