Having lived through a production datacenter meltdown due to software engineers throwing away TCP, along with stuff like slow start and congestion control, and obliterating ethernet switch buffers with UDP, I'm a bit concerned as to how QUIC is supposed to be used in order to avoid that?
If your fabric has end-to-end flow control this would be fine, but this seems like it could be greatly misused and should come with some warning labels.
That’s the hope, anyway. It’s hard to compete with decades of TCP refinement but at least there’s some big guns behind making this work.
There’s a lot of thought that has gone into QUIC and the protocol has several rules and mechanisms to prevent problems, such as the 3x amplification limit. Both the browser authors and server side (e.g. google) are on the lookout for problems and how they can improve on them.
If your fabric has end-to-end flow control this would be fine, but this seems like it could be greatly misused and should come with some warning labels.