SpringOne Platform 2017 Rossen Stoyanchev, Pivotal "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."

5. ??

6. Asynchronicity
Thread pools

7. Event loop
Coroutines
Actors
Asynchronicity
Thread pools
Fibers / Project Loom

9. Event
Loop

22. Tomcat, Jetty, …
Servlet API
Blocking I/O
Controller +
Reactive client

23. History of Servlet API

24. Controller +
Reactive client

25. Controller +
Reactive client

29. Blocking not expected
WebFilter WebHandler
Tomcat, Jetty, …Netty
Even Loop
WebFilter

30. WebFilter, WebHandler
Mono<Void>

31. Flux<DataBuffer> getBody()

32. writeWith(Flux<DataBuffer>)

33. Flux<DataBuffer> Flux<T>

40. ||

41. ||

50. 50

51. 51

53. 53