The document discusses the origins and principles of reactive programming. It originated in the 1960s with Jack Dennis's work on data flow concepts. Eric Meijer later coined the term "reactive programming" in 2010. The reactive manifesto principles of being responsive, resilient, elastic and message-driven are also covered. The document then explains Spring WebFlux and how it uses publishers like Flux and Mono to implement reactive programming. It shows examples of using parallelism in WebFlux and the Blockhound library for detecting blocking calls. Lastly, it proposes an exercise to convert an existing blocking web application to be reactive using WebFlux.
The document discusses the origins and principles of reactive programming. It originated in the 1960s with Jack Dennis's work on data flow concepts. Eric Meijer later coined the term "reactive programming" in 2010. The reactive manifesto principles of being responsive, resilient, elastic and message-driven are also covered. The document then explains Spring WebFlux and how it uses publishers like Flux and Mono to implement reactive programming. It shows examples of using parallelism in WebFlux and the Blockhound library for detecting blocking calls. Lastly, it proposes an exercise to convert an existing blocking web application to be reactive using WebFlux.
The document discusses the origins and principles of reactive programming. It originated in the 1960s with Jack Dennis's work on data flow concepts. Eric Meijer later coined the term "reactive programming" in 2010. The reactive manifesto principles of being responsive, resilient, elastic and message-driven are also covered. The document then explains Spring WebFlux and how it uses publishers like Flux and Mono to implement reactive programming. It shows examples of using parallelism in WebFlux and the Blockhound library for detecting blocking calls. Lastly, it proposes an exercise to convert an existing blocking web application to be reactive using WebFlux.
The document discusses the origins and principles of reactive programming. It originated in the 1960s with Jack Dennis's work on data flow concepts. Eric Meijer later coined the term "reactive programming" in 2010. The reactive manifesto principles of being responsive, resilient, elastic and message-driven are also covered. The document then explains Spring WebFlux and how it uses publishers like Flux and Mono to implement reactive programming. It shows examples of using parallelism in WebFlux and the Blockhound library for detecting blocking calls. Lastly, it proposes an exercise to convert an existing blocking web application to be reactive using WebFlux.
Webflux Eonics Hack Night #21 João Esperancinha [email protected] Origins 1960 Jack Dennis:
● Data Flows concepts during the 1960’s at MIT
● Data stream concept and iteractions ● Data Flow years 1974 – 1975 ● Roots in: ○ Asynchronous Digital Logic ○ Control Structures for Parallel Programming ○ Abstract Models for Concurrent Systems ○ Theory of Program Schemes ○ Structured Programming ○ Functional Programming
● Microsoft included C#, Visual Basic, LINQ, Volta ● Reactive programming framework ● Reactive Extensions for .NET. ● Dataflow programming on steroids
Ref: https://channel9.msdn.com/Blogs/Charles/Erik-Meijer-Rx-in-15-Minutes Reactive Manifesto Principles (applies to system and applications):
● Responsive ○ It needs to respond quickly. The time of the request itself is independent of this. ● Resilient ○ It must respond well and support Back-Pressure ○ Messages in control ○ Avoid catastrophic failure ● Elastic ○ Automatic Generation of resources. More threads in our case. ● Message Driven ○ Publisher/Subscriber
Ref: https://www.reactivemanifesto.org/ Spring WebFlux Basics Observer Pattern
Is a behavioral design pattern that lets you define a subscription mechanism to
notify multiple objects about any events that happen to the object they’re observing.
In other words, we are going to do declarative programming instead of imperative
programming.
Ref: https://en.wikipedia.org/wiki/Observer_pattern Spring WebFlux Publishers ● Flux Flux.just, Flux.from, Flux.fromIterable, ○ A publisher for a stream of objects Flux.fromArray, Flux.fromStream, ○ Used to create lists of objects] Flux.zip ○ Processes one stream end to end ○ Handles stream events ● Mono Mono.just, Mono.from, ○ A publisher for a single object Mono.fromCallable, Mono.zip, ○ Handles object events Mono.fromFuture, Mono.fromDirect, Mono.fromRunnable
Ref:https://docs.spring.io/spring/docs/current/spring-framework-reference/web- reactive.html Spring WebFlux Parallelism
Ref:https://docs.spring.io/spring/docs/current/spring-framework-reference/web- reactive.html Blockhound ● Test Library ● Needs to be installed: static { BlockHound.install(); }
.doOnNext(it -> { try { catController.getCatByIdI(1L); } catch (IOException e) { throw new RuntimeException(e); } }) .block(); Concerts Project Tests with JMeter ● Load tests ● Making the world a better place by registering thousands of Nicky Minajs 😉😉 {
"name": "Nicky Minaj",
"gender": "FEMALE",
"careerStart": 1000,
"birthDate": "a date",
"birthCity": "Port of Spain",
X 1000 / s "country": "Trinidad en Tobago",
"keywords": "Rap"
} Comparing Blocking MVC and Reactive MVC Results of analysis of Response Times Comparing Blocking MVC and Reactive MVC Results of analysis of number of requests: Label # Samples Average Min Max Std. Dev. Error % Throughput Received KB/sec Sent KB/sec Avg. Bytes
