Book Image

Learning RxJava - Second Edition

By : Nick Samoylov, Thomas Nield
Book Image

Learning RxJava - Second Edition

By: Nick Samoylov, Thomas Nield

Overview of this book

RxJava is not just a popular library for building asynchronous and event-based applications; it also enables you to create a cleaner and more readable code base. In this book, you’ll cover the core fundamentals of reactive programming and learn how to design and implement reactive libraries and applications. Learning RxJava will help you understand how reactive programming works and guide you in writing your first example in reactive code. You’ll get to grips with the workings of Observable and Subscriber, and see how they are used in different contexts using real-world use cases. The book will also take you through multicasting and caching to help prevent redundant work with multiple Observers. You’ll then learn how to create your own RxJava operators by reusing reactive logic. As you advance, you’ll explore effective tools and libraries to test and debug RxJava code. Finally, you’ll delve into RxAndroid extensions and use Kotlin features to streamline your Android apps. By the end of this book, you'll become proficient in writing reactive code in Java and Kotlin to build concurrent applications, including Android applications.
Table of Contents (22 chapters)
1
Section 1: Foundations of Reactive Programming in Java
5
Section 2: Reactive Operators
12
Section 3: Integration of RxJava applications
Appendix B: Functional Types
Appendix E: Understanding Schedulers

Action operators

The following are some helpful operators that can assist in debugging as well as getting visibility into an Observable chain. These are the action or doOn operators. They do not modify the Observable, but use it for side effects.

doOnNext() and doAfterNext()

The three operators, doOnNext(), doOnComplete(), and doOnError(), are like putting a mini Observer right in the middle of the Observable chain.

The doOnNext() operator allows a peek at each received value before letting it flow into the next operator. The doOnNext() operator does not affect the processing or transform the emission in any way. We can use it just to create a side effect for each received value. For instance, we can perform an action with...