Recommended
Recommended
More Related Content
What's hot
Similar to Impromptu orchestra: HTTP/2 and Reactive Streams
Similar to Impromptu orchestra: HTTP/2 and Reactive Streams (20)
Recently uploaded
Recently uploaded (20)
Impromptu orchestra: HTTP/2 and Reactive Streams
- 1. Impromptu Orchestra HTTP/2 and Reactive Streams berwout.devriesrobles@infosupport.com
- 2. Introductions Berwout de Vries Robles Info Support Professional Development Center
- 3. Topics • Short history of HTTP • Problems and past solutions • HTTP/2 Usage • Reactive Streams • Spring Reactor • Intro demo • Music performance • HTTP/3
- 4. Short history of HTTP
- 5. HTTP/0.9 • 1990~1991 • One line protocol • Designed for HTML documents • Request response GET /about/ <html><body><h1>It works!</h1></body></html> Request Response
- 6. HTTP/1.0 • 1991~1997 • Browsers emerge • Many differing implementations • HTTP-WG is formed
- 7. HTTP/1.0 Features of note • Request and response headers • Response status • Content types source: ytimg
- 8. HTTP/1.0 Request Host: http://twotruenoobs.com Accept: image/gif, image/jpeg, */* User-Agent: Mozzila/3.01 (Blank line) [------Optional request body----------] HTTP Verb Uniform Resource Identifier (URI) Version Headers Any data
- 9. HTTP/1.0 Response HTTP/1.0 200 OK Date: Sun, 15 Jul 2018 20:56:53 GMT Content-Length: 44 Content-Type: text/html (Blank line) <html><body><h1>It works!</h1></body></html> Status line Headers Any data
- 10. HTTP/1.1 • 1995~current • First formal standard by IETF • Publications in 1997, 1999 and 2014
- 11. HTTP/1.1 Features of note • Keepalive (default) • Chunked encoding • Cookies
- 12. Okay, what is the problem?
- 13. Problems • Extreme growth • Responsiveness • High volumes • Server sending
- 14. Responsiveness solutions • Polling • Long-polling • Websockets • Server sent events
- 15. HTTP/2.0 • 2012~current • Publication in 2015 • Based on SPDY by Google • Binary
- 16. HTTP/2.0 Features of note • Bidirectional • Header compression • Server push • Multiplexing source: Nginx
- 17. Great! how do we use it?
- 18. Using HTTP/2.0 • Implemented in webservers and browsers. • Web-applications don’t need to change! • All major browsers • All major webservers
- 19. Server push • Push is browser caches and webservers, not applications! • Defined using Link header Link: </assets/css/screen.css>; rel=preload; as=style source: GoLang blog
- 20. A new life for Server Sent Events • Multiplexing SSE • Multiple streams, one connection • No head of line blocking source: Nginx
- 21. Reactive streams
- 23. Main Goal: “To govern the exchange of stream data across an asynchronous boundary.” source: reactive-streams.org
- 24. source: OVHO • Composable • Flow control • Message/Music driven • Resilient • Responsive • Elastic • Asynchronous • Backpressure
- 25. Simplified • There are publishers • There are subscribers • Asynchronous streams in the middle • Reactive streams is a collection of interfaces source: Tech.io
- 26. Spring 5 and Reactor
- 27. Reactor • Flux = publisher • Mono = publisher • Processor = both • Subscriber = subscriber
- 28. Demo time
- 29. Time to make some music! • Turn on your sound (media) • Switch to 4G internet • Navigate to www.twotruenoobs.com • Username: ${name}-${section} for example: berwout-A • Roomname: jspring • Hit Join!
- 30. Difficulties • Naming is hard • Error handling on disconnects • Composability quickly becomes complexity
- 31. Do we still need websockets? • Large amount of support • Client sending a lot of individual requests • Large amounts of bi-directional data • Real-time
- 32. What does HTTP/3 bring? • TCP Limitations • QUIC • Multiple protocols • TCP over UDP source: Nginx
- 33. Setup source: Medium source: Rumbia source: Traefik source: Sounds electric source: IconFinder
- 34. Please rate my talk ☺ berwout.devriesrobles@infosupport.com