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

The traditional way of testing an Observable

Unit testing concentrates on a function to find out if the expected result matches with the actual result or not, under various probable situations. To test reactive components, we will start with a simple Observable which emits items, and tests whether the expected result matches with the actual or not. We will create Observable using the just() operator, emitting three items. We are also going to create a consumer which will add the items to an ArrayList instance. Later on, using the assertXXX() methods, we will cross-check the actual and expected values for the following test cases:

  • The list is not null
  • The list size is equal to three as our Observable is emitting three items
  • The second emitted item has the value equal to the actual value emitted by the Observable

The code for the preceding test cases is as follows:

    public...