Impromptu Orchestra
summary
Explains why HTTP/2 fixes HTTP/1.1 limits (binary frames, header compression, multiplexing) and reuses Server Sent Events as Reactive Streams over a single connection; shows a Spring Boot + Reactor demo that turns audience phones into an orchestra using an event-stream Flux/Processor, served from a Dockerized Spring backend and Angular front end behind a traffic proxy with Let’s Encrypt; achieves roughly 200–300 ms latency, scales to a 100-person live demo, and concludes Reactive Streams work for near‑real‑time updates though heavy bidirectional loads still favor WebSockets.
AI-written summary · about
chapters (17)
- 0:00Start
- 2:42HTTP/1.0 Features of note
- 3:13HTTP/1.0 Request
- 3:45HTTP/1.0 Response
- 4:31HTTP/1.1 Features of note
- 6:25Problems
- 7:19Responsiveness solutions
- 10:19HTTP/2.0 Features of note
- 12:15Using HTTP/2.0
- 12:43Server push
- 14:11A new life for Server Sent Events
- 14:46Websockets or Reactive Streams?
- 20:05Simplified
- 20:55Reactor
- 34:43Difficulties
- 37:16Playing music
- 37:59Traefik
