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

Understanding the Disposable interface

We discussed in depth about the emission of the items from Observable, which will be consumed by Subscriber. Not necessary all the emitted items every time needs to be consumed. It all depends on the scenario the developers are dealing with. We need to have a way to discard the resources which are in use. The Subscriber doesn't have such method. However, the Disposable interface provides the useful dispose() method. The Disposable interface is shown as follows:

      public interface Disposable {
void dispose(); boolean isDisposed();
}

The nonfunctional interface, Disposable, is now responsible for life cycle management of streams and resources. Now, subscribing Observable happens when someone uses DisposableObserver and to unsubscribe the dispose() method, it needs to be invoked which is analogous to the Subscription.cancel...