Speeding Up VKontakte’s Network Layer with HTTP/3
summary
The talk explains why VK moved from HTTP/2 to HTTP/3 (QUIC over UDP) to improve mobile network performance and reliability, especially on poor connections. It reviews limitations of TCP and HTTP/2, describes how QUIC/UDP addresses those issues, and details the practical steps and outcomes of implementing QUIC/HTTP3 in VK’s Android and iOS apps plus guidance for migrating your app to the new protocol.
AI-written summary · about
chapters (17)
- 0:00Introduction
- 1:33Why HTTP/3
- 4:04HTTP/2 problems and structure
- 7:13QUIC and HTTP/3
- 9:17DNS optimizations
- 13:27Connection optimizations
- 19:32Request optimizations
- 24:09Flow control
- 28:44Test results
- 30:52HTTP/3 server implementation
- 33:20Client-side libraries
- 36:30Cronet library for Android
- 38:17Setup and integration
- 39:22Protocol switching
- 40:28Implementation recommendations
- 41:31Missed topics and resources
- 42:20Q&A
related talks
46mHTTP/3: It's all about the transport!
30mHTTP/3 Is Next Generation HTTP. Is It QUIC Enough?
40mHTTP/3 - HTTP over QUIC is the next generation
34mHTTP/3 is coming
35mOn QUIC, HTTP/3 and tech stack unification
20mHTTP/3 in Envoy: End to End Acceleration
34mQUIC and HTTP/3: Too Big to Fail?!
43mDeploying and Debugging HTTP/3