Book Image

Learning RxJava

By : Thomas Nield
Book Image

Learning RxJava

By: Thomas Nield

Overview of this book

RxJava is a library for composing asynchronous and event-based programs using Observable sequences for the JVM, allowing developers to build robust applications in less time. Learning RxJava addresses all the fundamentals of reactive programming to help readers write reactive code, as well as teach them an effective approach to designing and implementing reactive libraries and applications. Starting with a brief introduction to reactive programming concepts, there is an overview of Observables and Observers, the core components of RxJava, and how to combine different streams of data and events together. You will also learn simpler ways to achieve concurrency and remain highly performant, with no need for synchronization. Later on, we will leverage backpressure and other strategies to cope with rapidly-producing sources to prevent bottlenecks in your application. After covering custom operators, testing, and debugging, the book dives into hands-on examples using RxJava on Android as well as Kotlin.
Table of Contents (21 chapters)
Title Page
Credits
About the Author
Acknowledgements
About the Reviewers
www.PacktPub.com
Customer Feedback
Preface

Understanding subscribeOn()


We kind of touched on using subscribeOn() already, but in this section, we will explore it in more detail and look at how it works.

The subscribeOn() operator will suggest to the source Observable upstream which Scheduler to use and how to execute operations on one of its threads. If that source is not already tied to a particular Scheduler, it will use the Scheduler you specify. It will then push emissions all the way to the final Observer using that thread (unless you add observeOn() calls, which we will cover later). You can put subscribeOn() anywhere in the Observable chain, and it will suggest to the upstream all the way to the origin Observable which thread to execute emissions with.

In the following example, it makes no difference whether you put this subscribeOn() right after Observable.just() or after one of the operators. The subscribeOn() will communicate upstream to the Observable.just() which Scheduler to use no matter where you put it. For clarity...