6 ms·
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 real
by giancarlostoro 4y ago
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.
Thanks to WSGI you can have projects like this that focus on scaling out your Python web all to the fullest extent possible.
- nicolaslem 4y agoThis. There was recently a trendy thread on HN about how great CGI was. WSGI is basically one of the spiritual successors to CGI: it's a simple way for a web server and a Python application to interact. It addresses one of the major shortcomings of CGI by not requiring to launch a new process for every request. 20 years later it is still going strong and is still by far the main way Python web apps are served.
- assume_role 4y agoDo python mains not know what FastCGI or mod_python are?
- nicolaslem 4y agoWSGI and mod_wsgi were designed as an improvement over mod_python which was pretty much an Apache only thing. As for FastCGI, although it is language agnostic it didn't really get traction outside of PHP.
- uranusjr 4y agoWSGI (same for ASGI) is a level above FastCGI (or CGI or whatever) in the stack; it exists so each Python web framework does not need implement ways to talk to CGI, FastCGI or whatever. Instead the framework implements a Python function, and the user can choose a WSGI server to wrap this Python function into whatever is needed to talk to any kind of language-agnostic gateways, including CGI, FastCGI, or even mod_python.
- nicolaslem 4y agoIn practice most deployments I have seen use a WSGI server that directly speaks HTTP so that CGI, FastCGI, or mod_python are not even necessary.
- linsomniac 4y agomod_python is pretty much dead at this point. Ubuntu 22.04 ships a port of it to Python 3, but it is buggy. I ended up switching my code from mod_python to WSGI instead of debugging "apache segfaulting in mod_python" issues, on some ~20 year old mod_python code over the last year. Pro tip: WSGI is pronounced like "whiskey". :-)
- aidos 4y agoIs it?? I’ve been slaughtering that word for almost 15 years. Whether true or not, that’s what I’m calling it from now on.
- linsomniac 4y agoIan Bicking is the one who told me, so I feel like I can speak with some authority. :-)
- masklinn 4y agolayer below and dead, respectively. The point of WSGI is for the server and application to speak the same python-level protocol. You can have a wsgi adapter on top of fcgi, though it’s really a waste of resources if you can skip fcgi entirely (which you usually can).
- simonw 4y agoI have a loos story I can tell that links mod_python to WSGI (a bit). One of the initial inspirations for creating the Django web framework back a the Lawrence Journal-World newspaper in ~2003 was that we wanted to start using Python on the web, but were concerned that mod_python didn't have quite enough existing users. What if it turned out not to work for us? So we designed a simple abstraction layer - a request and response object - as an insurance policy. If mod_python turned out not to work for us we could switch to something else without having to rewrite all of our code. At around about the same time the Python Web SIG formed - https://simonwillison.net/2003/Oct/18/pythonWebSIG/ https://simonwillison.net/2003/Oct/18/pythonWebSIG/ - and we joined it with the aim of helping define a standard similar to what we had been building for our own, private newspaper CMS. WSGI was the eventual result of that SIG - I didn't participate in the working group nearly as actively as I had planned to, so I can't say that I had much if any impact on the result. But hopefully this illustrates that yes, the people involved were very aware of mod_python back in 2003 when this work kicked off.
- whatever1 4y agoThank you so much for your work! It really shaped a generation of web development, giving a shot to small players and startups. PS That is why I love HN. You get to casually see creators of great projects.
- john-radio 4y agoSpeaking on behalf of the basic python main community, we just do whatever `requests` does.
- panzi 4y agoThat's a HTTP client library.
- laurencerowe 4y agoOne of the nice things about CGI was that by starting a new process per request it provided isolation between requests. Python's startup overhead obviously makes CGI untenable, but I find the new Web Assembly runtimes interesting because they are able to provide extremely fast startup by reseting state: https://bytecodealliance.org/articles/wasmtime-10-performance https://bytecodealliance.org/articles/wasmtime-10-performanc...
- nine_k 4y agoPHP was built around this idea for decades %) Theoretically one could produce ready-to-run, guaranteed clean Python request handlers very quickly. Run all the startup and imports stuff in a Python process, then freeze it. Fork a copy of it on a new request (with COW it's definitely fast), and terminate it normally after that. This would require some care, e.g. to not open sockets before the fork, so that handlers won't share it. I bet it has been tried, but I'm too lazy to actually search for that.
- laurencerowe 4y agoForking can be quite slow (milliseconds), though there are techniques to speed it up: https://www.cs.purdue.edu/homes/pfonseca/papers/eurosys21-odf.pdf https://www.cs.purdue.edu/homes/pfonseca/papers/eurosys21-od... I believe wasmtime can be faster as it doesn’t need to create as many new OS resources and just resets some memory maps. Only really meaningful for simple request handlers taking a few milliseconds.
- grubby 4y agoboiler up
- neilv 4y agoThe thread: "The beauty of CGI and simple design (rubenerd.com)" | 320 points by susam 9 days ago | 215 comments | https://news.ycombinator.com/item?id=34286622 https://news.ycombinator.com/item?id=34286622
- lucideer 4y ago> If you're doing Python web development and you have no idea what WSGI or ASGI are ASGI may be new to some, but... how is it possible to do Python web development without first learning what WSGI is? I haven't done much Python dev but WSGI seems to be the standard way - what's the less optimal alternative that people might end up with?
- dec0dedab0de 4y agoThere were other solutions 10+ years ago, but they're all dead. I guess the comment you're replying to was nervous because when people do python things in another language they sometimes don't follow python standards.
- giancarlostoro 4y agoSpot on! Sometimes even in Python people reinvent the wheel because they either had no idea something existed already, or they didn't like it for whatever reason. It also means writing your web framework differently depending on how their unique solution works, it does look like they did roll some enhancements over ASGI (they extended the spec) but the fact it still supports regular Python standards is good enough in my eyes.
- linsomniac 4y agoI assume the situation would be that you are just following a FastAPI or Django or Flask tutorial and putting the pieces together, running gunicorn without really even thinking about WSGI.
- beltsazar 4y ago> how is it possible to do Python web development without first learning what WSGI is? You'll be surprised to find out that there are many software developers who are "fast learners", but actually are shallow learners. Or to put it more kindly, they are not-so-curious learners, i.e. they only learn just enough things they need to accomplish the task at the moment. It's not necessarily a bad trait; but sometimes if you don't learn the fundamentals, it will cost you more (time, effort) along the way.
- duped 4y ago> 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 Unpacking the acronyms might help
- WhyNotHugo 4y agoI've thought a few times of trying to write a server in Rust that runs ASGI applications. The main oddity I found is that I'd end up with two asynchronous runtimes: one for the Rust webserver, and another for the python application itself. Somehow, this never sounded right, so I never gave it a shot. Granian sounds interesting. I'm not sure how you deal with the "two async runtimes" problem tho. Essentially, if you do non-blocking IO, then your processes start to become CPU-bound. So granian can eat up CPU on high load, and leave little CPU for the asgi application (or vice-versa). Somehow that doesn't sound right, but I also can't think of how you'd solve that.
- gi0baro-dev 4y agoGranian maintainer here. While it might sound "odd", actually having two runtimes running in two different threads is not so strange. This is actually what you end up when spawning multiple Python processes even with uvicorn: each process will have the asyncio event-loop running in the main thread. In Granian the Python runtime and the Rust ones communicate with each other in a non-blocking way, so – theoretically speaking – there's no additional CPU-bound load compared to a pure Python solution. Also, theoretically speaking, the only condition I can imagine where the two runtimes fight too much with each other is in case where you have a single core system with so poor performance to not handle 2 threads concurrently, which is probably so rare that we don't need to think about it.. Probably I should add some resource usage tests aside to benchmarks, but – again, theoretically speaking – if the Rust code is more efficient than the Python one, the final CPU usage should be lower, or more efficient.
- WhyNotHugo 4y agoThanks for your reply! Indeed, this should still be more efficient than a pure-python approach. My main confusion around this is: how do I scale threads? Say I have to CPU cores. Do you run one Granian thread and one python thread? I Granian under-uses CPU, Python can't use the excess. But if I run one Granian thread and two python threads, I risk Python leaving Granian with less CPU than it needs. In practice it should not be hard to find a balance... but somehow I'm still bothered by the fact that the design has no obvious solution for this.