Especially with increased concurrency/memory-sharing Purely speculating here, but I imagine Nginx's choice to split across worker processes (with separate pool

Especially with increased concurrency/memory-sharing Purely speculating here, but I imagine Nginx's choice to split across worker processes (with separate pools) instead of threads (with shared pools) had to do with a) avoiding memory errors due to sharing resources, b) reducing extra (defensive) locks, and/or c) reducing the blast-radius of crashes All of which Rust helped the team not to have to worry about, enabling more sharing of resources, which solved their main bottleneck Of course the OP's JVM solution would be memory-safe too (helping with (a)), but then that comes with other costs