202
HTTP/2
Many requests on one connection. It removes a class of blocking and does not make a slow server fast.
What is HTTP/2?
HTTP/2 multiplexes streams on one TCP connection, compresses headers, and allows the server to push (rarely worth it). It does not fix a slow database. One lost packet can still stall all streams on that connection. HTTP/3 moves this to UDP for that reason.
Why does HTTP/2 matter when vibe coding?
Models turn on HTTP/2 and expect the N+1 API to disappear. The round trips moved. They did not go away if the client still waits serially.
How do you do HTTP/2?
Enable it at the proxy. Keep the number of requests modest. Do not serialize calls that can overlap. Do not assume push is a design.
How do you ask a model for HTTP/2?
Serve (site) over HTTP/2 at the proxy. Do not serialize independent API calls. Do not add more requests just because multiplexing exists. HTTP/2 is not a fix for a slow handler.
What goes wrong with HTTP/2?
HTTP/2 to the client and HTTP/1.1 with one connection to a tiny upstream pool. You unblocked the browser and blocked the proxy.