IntermediatePhone
2 min
HTTP/1.1 vs HTTP/2
HTTPPerformanceWeb
Advertisement
Interview Question
Name two key improvements HTTP/2 brings over HTTP/1.1 and why they matter.
Key Points to Cover
- Multiplexing to avoid head-of-line blocking per connection
- Header compression (HPACK) reduces overhead
- Server push (optional) and prioritization can improve latency
Evaluation Rubric
Mentions multiplexing benefits40% weight
Explains header compression30% weight
Connects features to latency gains30% weight
Hints
- 💡Many stacks disable server push today; still OK to mention.
Common Pitfalls to Avoid
- ⚠️Focusing solely on the 'what' (e.g., 'it has multiplexing') without explaining the 'why' or the tangible impact (e.g., 'why multiplexing matters for Head-of-Line blocking').
- ⚠️Confusing HTTP/2's connection model (single TCP) with HTTP/3's (QUIC over UDP).
- ⚠️Overlooking the significance of header compression, especially its impact on bandwidth for small, frequent requests.
- ⚠️Incorrectly attributing features like connection keep-alive or pipelining (which existed in HTTP/1.1 with limitations) as HTTP/2 innovations.
- ⚠️Not mentioning or incorrectly describing Head-of-Line blocking and its resolution in HTTP/2.
Potential Follow-up Questions
- ❓How does HTTP/3 differ?
- ❓How many TCP connections are typical per origin?
Advertisement