By resources do you mean hardware resources or expertise or what? Cause running more than 2 processes on a 2-core server just sounds weird. I thought Node's d

By resources do you mean hardware resources or expertise or what? Cause running more than 2 processes on a 2-core server just sounds weird. I thought Node's doctrine was "One process per core", and (async) Rust and Go seem to do fine with managing their own thread pools. I haven't _tried_ to do a realistic benchmark of Hyper, but I've never seen it struggle with concurrency either, even on long-polling applications where concurrency was the norm for all clients. More processes would work, but it doesn't seem like the right layer of abstraction for 2015, now that Nginx and Node have made the event model so popular.