News for hackers. Stuff that matters.

A comment on There Isn't Much Point to HTTP/2 Past the Load Balancer. Parent comment

Re:There Isn't Much Point to HTTP/2 Past the Load Balancer by dgoldstein0 on Thursday February 27, 2025 @10:34PM (#43201422)
I think the more common architecture is for edge network to terminate SSL, and then transmit to the load balancer which is actually in the final data center? In which case you can http2 or 3 on both those hops without requiring it on the application server.

That said I still disagree with the article's conclusion: more connections means more memory so even within the same dc, there should be benefits of http2. And if the app server supports async processing, there's value in hitting it with concurrent requests to make the most of its hardware, and http1.1 head of line blocking really destroys a lot of possible perf gains when the response time is variable.

I suppose I haven't had a true bake off here though - so it's possible the effect of http2 in the data center is a bit more marginal than I'm imagining.

[ Parent | on HN ]
Re:There Isn't Much Point to HTTP/2 Past the Load Balancer by hansvm on Friday February 28, 2025 @02:18AM (#43202685)
HTTP2 isn't free though. You don't have as many connections, but you do have to track each stream of data, making RAM a wash if TLS is non-existent or terminated outside your application. Moreover, on top of the branches the kernel is doing to route traffic to the right connections, you need an extra layer of branching in your application code and have to apply it per-frame since request fragments can be interleaved.
[ Parent | on HN ]