My first thought was "this better be WSGI!!!" and sure enough it is. If you're doing Python web development and you have no idea what WSGI or ASGI are, you really ought to learn more about them. ASGI is the Async equivalent / answer to WSGI. It is one of the main ways to deploy any web application in Python. Every major web framework supports it OOTB and heck, even one of the fastest web frameworks for Python (FastAPI) uses it exclusively.<p>Thanks to WSGI you can have projects like this that focus on scaling out your Python web all to the fullest extent possible.
Looks super interesting. One of the things that I wanted to improve on are Gunicorn's latency and here:<p><a href="https://github.com/emmett-framework/granian/tree/master/benchmarks">https://github.com/emmett-framework/granian/tree/master/benc...</a>
shows way better latency for Granian.<p>Kudos.<p>just, when would you consider this good enough for production?
There is a similar project <a href="https://github.com/sansyrox/robyn">https://github.com/sansyrox/robyn</a><p>A framework for Python, the core of which is written in Rust
Serious question: why would I want to use this? Is the answer as simple as “because I want to develop in Python”?.<p>Because if you’re going to do it in Rust, why not just go all the way with something like Axum?<p>That being said, first time I hear about WSGI/ASGI, so I did some reading. From an educational perspective I’m intrigued and even will check the codebases at some point to see how it works.<p>But from a production POV I do not get why I would want to use it. What’s so great about it - besides letting you develop a reasonably fast server in Python, surely it is more then that?
Python comes with an HTTP server built-in!<p><a href="https://docs.python.org/3/library/http.server.html" rel="nofollow">https://docs.python.org/3/library/http.server.html</a>