Not as bad as you think, for an application server anyway. HN actually uses a thread per request according to the docs: https://arclanguage.github.io/ref/srv.ht

Not as bad as you think, for an application server anyway. HN actually uses a thread per request according to the docs: https://arclanguage.github.io/ref/srv.html https://arclanguage.github.io/ref/srv.html They also read from disk for most requests. So, thread per request and also reading from disk. I worked at one company where we had many dozens of services with thrift/spring boot and spawned a request per thread and it worked fairly well. We were collecting and aggregating every review on the internet (for our customers), and had dozens of services... There were a couple in a reactive style. So we took the maintenance cost when we needed to.