Managing two million web servers
You don't need to "crash the server" in response to an error from a single user - It is sufficient to just close the connection and destroy the session.<p>I doubt that erlang spawns millions of OS processes because that would be extremely inefficient due to CPU context switching. So in reality, all erlang is doing behind the scenes is closing the connection and destroying the session... It's not actually crashing and restarting any processes... You can easily implement this behavior with pretty much any modern server engine such as Node.js and tornado.