This document discusses Reactive Streams, which is an asynchronous programming model for processing streams of data in a non-blocking manner. It introduces key concepts like back pressure to control resource usage, and implementations like Project Reactor that provide reactive APIs using Mono and Flux to represent asynchronous data streams. Reactive Streams provide benefits like composability, efficiency through back pressure, and the ability to work with both single-item and sequenced data streams in a reactive and asynchronous way.
2. Humberto Streb
- software developer
- falling in love with distributed systems
- half-assed goalkeeper ;(
fb.com/humbertostreb
twitter.com/humbertostreb
github.com/hstreb
17. - Composability and readability
- Data as a flow manipulated with a rich vocabulary of operators
- Nothing happens until you subscribe
- Backpressure
- High level but high value abstraction that is concurrency-agnostic
From Imperative to Reactive Programming
34. More
- Spring 5.0 with reactive support
https://www.brighttalk.com/webcast/14893/277207
- Deal with JDBC blocking
https://dzone.com/articles/spring-5-webflux-and-jdbc-to-block-or-not-to
-block