Servlet or Reactive Stacks: The Choice is Yours. Oh No... The Choice is Mine! - Rossen Stoyanchev
summary
Compares Spring MVC (Servlet) and Spring WebFlux (Reactive) by running a car-reservation demo that actually works: a MongoDB Flux of cars, a WebClient making nested POSTs with a 2–5 second simulated booking delay, and a Netty server using four Reactor Netty threads to handle both server and client work. Shows Servlet apps can use reactive clients and stream responses but must block on the servlet layer, while WebFlux supports true non-blocking I/O and functional endpoints only on WebFlux, including bidirectional streaming and backpressure.
AI-written summary · about
chapters (36)
- 0:00Introduction
- 2:04Change
- 2:54Synchronicity
- 6:43Misconceptions
- 8:42Event Loop
- 9:37Reactive Libraries
- 12:18Java 8 Lambda
- 13:10Why Choice Matters
- 14:39How Weve Created Choice
- 16:11Tomcat Jetty
- 17:26Demo Application
- 29:29Async Support
- 30:33Nonblocking IO
- 31:35Nonblocking Frameworks
- 33:19surveyed API
- 33:32internal processing
- 35:07concurrency
- 36:21nonblocking
- 37:19flux
- 38:35codecs
- 43:33Switching Threads
- 44:09Collector List Operator
- 45:34Application Stream JSON
- 47:04Reactive Streams Demo
- 48:45Reactive Data Report Demo
- 49:48Reactive Web Client Demo
- 51:11Flux Interval Demo
- 53:14The Choice is Mine
- 54:00Spring MVC and Spring Wet Flux
- 54:22Consistency and continuity
- 55:23The range of options
- 55:51The obvious
- 56:23This is a game
- 57:18Using reactive clients
- 57:56When to consider web flex
- 59:29Functional programming model
