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)

SpringWebFlux for Microservices

Up until this point, we have discussed Reactor as a standalone framework. We have also seen how we can build publishers and subscribe to them. Reactor is well suited to handling the exchanging of large volumes of data, but it is important to note that Reactor is not limited to standalone programming only; it can also be used to build web applications.

Traditionally, we built enterprise-grade web applications using the SpringMVC framework, a synchronous and blocking framework from the Spring ecosystem. SpringMVC can also serve asynchronous non-blocking data using Servlet 3.1, but then it moves away from the concepts of request mappers and filters. This makes the framework quite difficult to work with. Furthermore, when building microservice architecture for high performance, the framework may not be the optimum choice. With such an architecture...