Book Image

Hands-On Reactive Programming with Reactor

By : Rahul Sharma
Book Image

Hands-On Reactive Programming with Reactor

By: Rahul Sharma

Overview of this book

Reactor is an implementation of the Java 9 Reactive Streams specification, an API for asynchronous data processing. This specification is based on a reactive programming paradigm, enabling developers to build enterprise-grade, robust applications with reduced complexity and in less time. Hands-On Reactive Programming with Reactor shows you how Reactor works, as well as how to use it to develop reactive applications in Java. The book begins with the fundamentals of Reactor and the role it plays in building effective applications. You will learn how to build fully non-blocking applications and will later be guided by the Publisher and Subscriber APIs. You will gain an understanding how to use two reactive composable APIs, Flux and Mono, which are used extensively to implement Reactive Extensions. All of these components are combined using various operations to build a complete solution. In addition to this, you will get to grips with the Flow API and understand backpressure in order to control overruns. You will also study the use of Spring WebFlux, an extension of the Reactor framework for building microservices. By the end of the book, you will have gained enough confidence to build reactive and scalable microservices.
Table of Contents (13 chapters)

Error recovery

In the preceding section, we determined how to configure an error callback. However, when performing error handling, we may encounter cases in which we want to continue execution with some alternative values. There are many use cases for such scenarios. For example, quote aggregating systems can have errors thrown while getting the latest tick value, but the aggregation must continue with the last value. In the following sections, we will cover each of the operators offered, in order to accomplish this.

The onErrorReturn operator

Reactor provides the OnErrorReturn operator to provide a fallback value in the event of an error. As a result of the fallback, the original error event is not propagated to the error...