Re:Go vs. Python for a simple web server
by justincormack on Wednesday June 22, 2011 @10:21AM
(#2683213)
That confusion is because there are a lot more options now, what with there being embedded (performant) HTTP libraries so you can run your stack without a separate server, or you can embed user code into a traditional server, or many other combinations. Async stacks do not a bit in the middle. And some NoSQL databases like Couch can embed the web server and middle parts of the code.
Go has an interesting combination of lightweight threading and a high quality performant HTTP server, so potentially it is good for implementing the http serving and application layers.
It seems these days that there is a confusion between the web server (often a reverse-proxy), the web application and the thing in the middle (gateway/pipe/container/app server). While I would certainly consider Go for the implementation of a reverse-proxy or an app server, it isn't clear that Go is a good choice for the web application itself, especially when you consider that most of the time is spent in the DB and in the cache...
Anway, the article mostly talked about Go and not about Python...