3 ms·

Go is the prime example. For example, in your typical web application a Goroutine is spawned for every incoming connection. This basically gives you a dedicate

Go is the prime example. For example, in your typical web application a Goroutine is spawned for every incoming connection. This basically gives you a dedicated runtime for each simultaneous connection. In Node or Python, this would be the equivalent of starting a whole new process for every request. But in Go, there's very little cost to doing it this way. The advantage is that each connection basically never blocks waiting for another user. In Node and Python, we talk about handling tens to hundreds of requests per second per server. In Go, we talk about handling thousands to tens of thousands per second. It's just orders of magnitude more throughput.

ntr-- 4y ago
Can't comment on Python, but I once worked on a Node.js codebase that could only handle tens of requests per second, it was highly unusual and doing some incredibly dumb things like pinging out to Redis to check for DDOS protection counters before starting to serve any request. See: https://www.fastify.io/benchmarks/ https://www.fastify.io/benchmarks/ Node is more susceptible to poor code and out of band IO slowing it down, but the V8 runtime itself is cpp and simple services are close to just writing decorators over a cpp webserver. It's obscenely fast and good enough for most purposes.