HTTP/1.1 vs HTTP/2

Question

Name two key improvements HTTP/2 brings over HTTP/1.1 and why they matter.

Accepted Answer

HTTP/2 represented a significant evolution over HTTP/1.1, fundamentally optimizing how web resources are transported. Two of its most crucial improvements revolve around enhancing efficiency and reducing latency through optimized connection utilization and reduced data overhead. Firstly, HTTP/2 introduced **full request and response multiplexing** over a single TCP connection. Unlike HTTP/1.1, where a single connection could only handle one request and response at a time, leading to application-layer Head-of-Line (HOL) blocking, HTTP/2 allows multiple requests and responses to be interleaved asynchronously on a single connection. This eliminates the need for browser-side workarounds like domain sharding, drastically reduces latency, improves network utilization, and ensures faster loading by preventing less critical assets from blocking crucial ones. Secondly, HTTP/2 implemented **header compression using HPACK**. In HTTP/1.1, headers were sent as plain text with every request and response, often redundantly, consuming significant bandwidth. HPACK addresses this by utilizing static and dynamic tables, along with Huffman encoding, to compress header fields. This means that common headers or those already seen in a session are not resent entirely, significantly reducing the overhead of each request and response, especially for small, frequent transactions, thereby saving bandwidth and accelerating communication. Finally, HTTP/2 also brought **Server Push and Stream Prioritization**. Server Push allows the server to proactively send resources to the client that it knows the client will need, without waiting for the client to explicitly request them, such as CSS or JavaScript files. This eliminates additional round trips and significantly reduces perceived load times. Coupled with stream prioritization, clients can signal the relative importance of different resources, allowing the server to optimize the delivery order, ensuring critical content is rendered as quickly as possible. These innovations collectively made HTTP/2 a cornerstone for modern web performance, leading to faster, more efficient, and more responsive user experiences. Its profound impact on reducing latency and improving resource utilization has been a key enabler for today's rich web applications.

HTTP/1.1 vs HTTP/2

HTTP Keep-Alive & Connection Pooling

HTTP Idempotent Methods

Purpose of a CDN

Sudden 5xx Spike on Web Tier

Common HTTP Status Codes

Edge Computing Meets Edge Caching: Building Real-Time Applications at the Network Edge

Paginated vs. Bulk API Calls: Performance, Cost, and Reliability Trade‑offs

Edge Compute with CDNs: Caching, Workers, and Safe Gradual Rollouts