As posed, this problem is a toy one and fairly easy. 1) The arrival rate is constant, vs the more realistic Poisson distribution 2) The response fits in a sin

As posed, this problem is a toy one and fairly easy. 1) The arrival rate is constant, vs the more realistic Poisson distribution 2) The response fits in a single packet 3) Requests are consistent size. I don't think most companies are going to have the resources to take advantage of QUIC and HTTP/3 for a while. While head of line blocking is theoretically gone, most programming is based around ordered delivery. I see lots of projects doing single streams to minimize complexity, but that severely reduces large asset transfer. I am sure the FAANG crew will gain a lot of advantages, but tooling needs to be there for the rest of us. Obviously some will take advantage of it, but it is a shift in responsibility to the application and dealing with window scaling and out of order delivery is expensive. IMHO, UDP is simply a target because legacy systems would make a new option that was superior difficult if impossible to implement. As I have supported voip and streaming over the public Internet, I admittedly have a jaded view. But I am not looking forward to supporting the quirks of every client when it was easy to hand that off to the OS. Hopefully I am wrong, and SWEs will be good at dealing with ood and random failures and standards will offload the cost of implementing what TCP gave us for free. But I don't think people realize how easy reliable, ordered delivery makes programming.