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)

Chapter 6: Dynamic Rendering

  1. How does the SpringWebFlux framework resolve a View?

The framework invokes ViewResolutionResultHandler using the HandlerResult returned for the endpoint invocation. ViewResolutionResultHandler then determines the correct view by validating the returned value for the following:

  • String: If the returned value is a string, then the framework builds a view using the configured ViewResolvers
  • Void: If nothing is returned, it then tries to build the default view
  • Map: The framework looks for the default view but it also adds the key values returned into the request model

ViewResolutionResultHandler looks up the content type passed in the request. In order to determine which view should be used, it compares the content type passed to the content type supported by ViewResolver. It then selects the first ViewResolver, which supports the request content type...