Servlet or Reactive Stacks: The Choice is Yours. Oh No... The Choice is Mine! - Rossen Stoyanchev

Spring Framework 5.0 provides a choice of two web stack. One is the existing Servlet based Spring MVC and the other is the Reactive Streams (and Reactor) based Spring WebFlux that also supports non-Servlet containers such as Netty and Undertow. To make the choice even more interesting in 5.0 Spring MVC also supports the use of reactive libraries for orchestrating remote HTTP service calls, using reactive data repositories, and so on.
In this session we'll try and make sense of these options by comparing the execution models of each stack in the context of several common web application scenarios as well as some additional scenarios that have been harder to do on a traditional Servlet stack.
The session will you help you to understand just how much reactive mileage you can get out of your Servlet stack and what more you can do with a reactive stack. We'll use sample code to demonstrate reactive features and behavior (e.g. back pressure) on each stack.
Knowledge of using reactive libraries such as Reactor or RxJava is very helpful but not required for this session.
Rossen Stoyanchev, Spring Framework Developer, Pivotal
Filmed at SpringOne Platform 2017

[@SaidOTwentySix]

Thank you Rossen, your presentations are so intuitive !

[@ArifOctovian]

Thank you for the talk.
I felt we need more like this 'behind' the scene talk.

[@T0mGa1]

Great talk - very nice way of explaining possible solutions, the changes've been made and the reasons behind them !

[@ZoltanAltfatter1]

awesome talk

[@dungthong7480]

good present and explanation, thanks to give me more outlook and understanding around reactive stacks. Great job

[@aballant38]

For those looking for the code, the link given is github.com/rstoyanchev/demo-reactive-spring

[@Ryaner88]

Source code github.com/rstoyanchev/demo-reactive-spring

[@Kerai121]

If anyone is looking for demo project.
github.com/rstoyanchev/demo-reactive-spring

[@USONOFAV]

Speaker doesn't really understand what event loop is and why event loop style of processing only needs fewer threads.