HTTP/2
A major revision of HTTP that adds multiplexing (multiple requests over one connection), header compression, and server push. Much faster than HTTP/1.1 for modern web apps.
What is HTTP/2?
A major revision of HTTP that adds multiplexing (multiple requests over one connection), header compression, and server push. Much faster than HTTP/1.1 for modern web apps.
HTTP/2 is a intermediate-level concept that sits in the API Design & Protocols area of system design. Engineers reach for it whenever they need to reason about real-world trade-offs in that space — not just for textbook correctness, but because real production systems at companies like Netflix, Amazon, and Google make these decisions every day.
If you want to go deeper than this definition — with diagrams, code, and a quiz to lock it in — work through the "HTTP/2" lesson linked below. It walks through the why, the mechanism, the trade-offs, and how the giants actually use it in production.
Learn HTTP/2 in depth
Full interactive lesson with diagrams, code examples, real-world references, and a quiz.
Open the HTTP/2 lessonRelated lessons
Lessons that touch on HTTP/2 as part of a larger topic.
HTTP/2 Multiplexing
Multiple requests over one connection, how HTTP/2 eliminated head-of-line blocking at the application layer
intermediate · api design protocols
gRPC
Google's high-performance RPC framework, binary protocols, HTTP/2 streaming, and auto-generated clients
intermediate · api design protocols
See also
Related glossary terms you might want to look up next.
HTTP
The protocol powering the web. A request-response model where clients ask for resources and servers respond. Stateless by design.
gRPC
A high-performance RPC framework by Google using Protocol Buffers and HTTP/2. Much faster than REST for service-to-service communication.
TCP
A reliable transport protocol that guarantees data arrives in order and without errors. It uses a three-way handshake to establish connections.