Spring Reactive Programming Module1
Uploaded by
youtubepremiumSpring Reactive Programming Module1
Uploaded by
youtubepremiumSpring Reactive Programming - Module 1: Introduction
Overview
Reactive Programming is a programming paradigm that is asynchronous, non-blocking, and event-driven. It
deals with data streams and the propagation of change. This model allows applications to scale effectively,
especially for I/O-heavy operations.
Why Reactive?
- Traditional apps block threads while waiting (e.g., for I/O, DB, etc.)
- Reactive apps use fewer threads, allowing high throughput with minimal resources
- Ideal for microservices, event-driven systems, and cloud-native apps
Reactive Manifesto - Core Concepts
- Responsive: Responds in a timely manner
- Resilient: Handles failure gracefully
- Elastic: Adapts to varying load
- Message-driven: Uses asynchronous message-passing
Core Building Blocks
- Publisher: Emits data (Mono/Flux)
- Subscriber: Consumes data
- Backpressure: Slows producer if consumer overwhelmed
- Operators: Transform streams (map, flatMap, etc.)
Spring Reactive Programming - Module 1: Introduction
Imperative vs Reactive Code
Imperative:
String name = getName(); // blocks
System.out.println(name);
Reactive:
Mono<String> nameMono = getNameAsync(); // async
nameMono.subscribe(System.out::println);
Project Reactor Basics
Spring WebFlux is powered by Project Reactor, which introduces Mono and Flux.
- Mono: Emits 0 or 1 item
- Flux: Emits 0 to N items
Mono Example
Mono<String> mono = Mono.just("Hello Reactive World");
mono.subscribe(System.out::println);
Flux Example
Flux<String> flux = Flux.just("Spring", "Reactive", "Programming");
flux.subscribe(System.out::println);
Spring Reactive Programming - Module 1: Introduction
Backpressure
Backpressure allows the subscriber to signal to the publisher that it cannot keep up with the rate of
emissions. Flux and Mono follow the Reactive Streams specification that supports backpressure.
Use Cases
- Streaming APIs
- WebSockets / SSE
- IoT platforms
- Microservices under heavy load
- High-concurrency apps
Interview Questions
