HTTP/3 and Reactive Streaming
summary
Argues that HTTP/3 (QUIC + TLS 1.3) removes HTTP/2 head‑of‑line blocking and enables per-request QUIC streams with connection resumption, improving mobile latency. Builds a reactive pipeline using Spring WebFlux, Server‑Sent Events and an Angular client; server runs on a tiny home node behind Traefik, serving per‑instrument MIDI samples to phones. Live demo streams 15 instruments to about 50 phones (roughly 250 connections) over a 6 Mbps upload; demo mostly works but suffers intermittent Internet and audio-sample quality issues.
AI-written summary · about
chapters (11)
- 0:00Introduction and setup
- 2:50HTTP basics recap
- 8:28HTTP/1.1 and HTTP/2 issues
- 11:37HTTP/3 fundamentals
- 20:53HTTP/3 benefits and challenges
- 22:17Reactive streaming basics
- 28:18Reactive types in Java
- 30:30Live reactive demo introduction
- 35:51Demo execution and results
- 41:04Summary and future outlook
- 42:20Q&A session
related talks
39mImpromptu Orchestra
46mHTTP/3: It's all about the transport!
51mHTTP/3 and QUIC: Who, what, where, when and, WHY?
30mThere and back again: reinventing UDP streaming with QUIC
37mHTTP/3: why and where are we?
30mHTTP/3 Is Next Generation HTTP. Is It QUIC Enough?
34mHTTP/3 is coming
35mOn QUIC, HTTP/3 and tech stack unification