When is concurrency an issue?
At what point/scale does concurrency become an issue in a web server?
I followed Primeagen's videos comparing Rust, Go, and Node and I take his point that Rust is more performant.
But at what scale does this matter?
I know netflix and other huge co's write node/restify servers and I imagine they wouldn't do that if they were incurring huge performance hits.
If you were to write a t3 app, is there a point at which it just starts to shit the bed?
3 Replies
Unknown User•2y ago
Message Not Public
Sign In & Join Server To View
This is a really really good answer, thank you!
I think it's clicking now: if the underlying language/framework is less efficient at handling requests then you need more resources to handle the same number of requests by scaling horizontally in the cloud.
And I agree: the t3 stack is the easiest way to go from 0 to 1. I'm having a lot of fun building with it.
Unknown User•2y ago
Message Not Public
Sign In & Join Server To View