Spring in a Reactive Era

Reactive programming is becoming common knowledge and being used more and more.

Spring 5.0 introduced the ability to build reactive web application by introducing Spring WebFlux, other projects like Spring Data and Spring Security quickly followed. We will take a look in how the reactive story in Spring evolved from 5.0 throughout 5.2.

We will also take a look at what it does take to be truly reactive. The whole stack should be reactive from web to data persistence.

Transcript

1. Spring in a Reactive era Marten Deinum
 
 5 September 2019
2. Who am I
3. “In a nutshell reactive programming is about non-blocking, event-driven applications that scale with a small number of threads with backpressure as a key ingredient that aims to ensure produces do not overwhelm consumers.” Rossen Stoyanchev, Project Reactor Team
4. Reactive Streams “The purpose of Reactive Streams is to provide a standard for asynchronous stream processing with non-blocking backpressure” https://github.com/reactive-streams/reactive-streams-jvm
5. Reactive Streams - Just 4 Interfaces • Publisher<T> • Subscriber<T> • Subscription • Processor<T,R>
7. Spring 5.0 - The Reactive Story • Initial Reactive Support • Spring WebFlux (support for Project Reactor & RxJava) • WebClient as replacement for AsyncRestTemplate • Spring Security • Spring Data
9. Spring 5.1 - The Reactive Story • Improved Reactive Support • Spring WebFlux Improved • WebSocket support • Spring Security • Spring Data
11. Spring 5.2 - The Reactive Story • Improved Reactive Support • Spring WebFlux improvements • RSocket Support • Reactive Transaction Management • Spring Security • Includes RSocket Support • Spring Data
13. Programma Datum: Maandag 16 september 2019 Locatie: Kantoor Conspect Tijd: 18:00-19:00 Inloop met een hapje en drankje 19:00-20:30 Sessie R2DBC door Mark Paluch 20:30-21:30 Borrel en netwerken Reactive Relational Database Access