Book Image

Reactive Programming With Java 9

By : Tejaswini Mandar Jog
Book Image

Reactive Programming With Java 9

By: Tejaswini Mandar Jog

Overview of this book

<p>Reactive programming is an asynchronous programming model that helps you tackle the essential complexity that comes with writing such applications.</p> <p>Using Reactive programming to start building applications is not immediately intuitive to a developer who has been writing programs in the imperative paradigm. To tackle the essential complexity, Reactive programming uses declarative and functional paradigms to build programs. This book sets out to make the paradigm shift easy.</p> <p>This book begins by explaining what Reactive programming is, the Reactive manifesto, and the Reactive Streams specifi cation. It uses Java 9 to introduce the declarative and functional paradigm, which is necessary to write programs in the Reactive style. It explains Java 9’s Flow API, an adoption of the Reactive Streams specifi cation. From this point on, it focuses on RxJava 2.0, covering topics such as creating, transforming,fi ltering, combining, and testing Observables. It discusses how to use Java’s popular framework, Spring, to build event-driven, Reactive applications. You will also learn how to implement resiliency patterns using Hystrix. By the end, you will be fully equipped with the tools and techniques needed to implement robust, event-driven, Reactive applications.</p>
Table of Contents (12 chapters)
Free Chapter
1
Introduction to Reactive Programming

Patterns used by Hystrix

The following are the common patterns used for HystrixCommand and HystrixObservableCommand:

Fail-fast

As per application designing, when the failure or condition to fail happens, it is immediately reported to the system. Fail-fast systems are designed so that the normal operation will stop instead of continuing. The system is designed in such a way that often checks, at several points will be done, to detect any failures. A fail-fast module doesn't handle the error; rather, it passes the responsibility to the next level of the system.

The very simple thing that as a developer we can do is to implement fail-fast, in our Hystrix system and not to provide any fallback mechanism. Yes! Don't override...