It's only "thread per connection" in very, very basic servers. If you are interacting with other services, it becomes thread per inbound connection, and thread per outbound request (to support retries and cancellation), and then coordinating threads for fanout of requests, etc.
-
-
-
I’m certainly willing to believe that async I/O is a more convenient programming model for cancellation, etc.
End of conversation
New conversation -
-
-
Well, and doesn't Rust have the same 64k limit of running threads like the other languages ?? This is why a lot of Kotlin and Java devs, try to stick to Vert.x and other asynchronous frameworks and we totally sacrifice readability for scalability
-
There is no 64K limit.
- 2 more replies
New conversation -
-
Show additional replies, including those that may contain offensive content
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.