News for hackers. Stuff that matters.
Re:Why HTTP/3 is eating the world by redundantly on Thursday October 05, 2023 @09:36AM (#37778436)
<insert 'Why Don't We Have Both?' meme here>

Joking aside, we should be happy for any improvement that can be obtained. A single second saved for a single connection on its own is insignificant, but dozens or hundreds of connections for a single user, multiplied by the thousands or possibly millions of users, that's a huge amount of time saved.

Re:Why HTTP/3 is eating the world by djha-skin on Thursday October 05, 2023 @09:59AM (#37778723)
Sure, yeah, it's all sunshine and roses for the client, but I'm a DevOps engineer. It is very difficult on the server side.

You can enable it on CDNs pretty easily these days, but enabling it on the API side is more difficult. The nginx ingress controller for kubernetes doesn't support HTTP3 yet. It supports HTTP2, but I've heard that you can get into trouble with timeouts or something if you don't tune HTTP2 right. It does look like it's doable though, certainly more doable than HTTP3.

HTTP2 is a moderate lift from a systems administration standpoint, but it's also a risk. It means changing the infrastructure enough that outages can occur, so that I'd rather do this lift when things are more stable and the holiday season is over.

Re:Why HTTP/3 is eating the world by redundantly on Friday October 06, 2023 @10:28AM (#37791233)
Complaining that things are harder for the engineers than the end users is a non-starter for me.

Complaining about how difficult it can be to configure nginx when automation is a huge thing right now is also a non-starter. Figure it out once, automatically configure it for the rest of the endpoints. This complaint is made even worse by you calling yourself a devops engineer.

The worst part, though, is you appear to be complaining about something you've had yet to implement. Like I told my kids when they were young: you haven't tried supper yet, you don't know if you like it or not.