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

Summary


This was probably our most intense chapter yet, but it provides a turning point in your proficiency as an RxJava developer as well as a master of concurrency! We covered the different Schedulers available in RxJava as well as ones available in other libraries such as RxJavaFX and RxAndroid. The subscribeOn() operator is used to suggest to the upstream in an Observable chain which Scheduler to push emissions on.  The observeOn()will switch emissions to a different Schedulerat that point in the Observable chain and use that Scheduler downstream. You can use these two operators in conjunction with flatMap() to create powerful parallelization patterns so you can fully utilize your multi-CPU power. We finally covered unsubscribeOn(), which helps us specify a different Scheduler to dispose operations on, preventing subtle hang-ups on threads we want to keep free and available even if they call the dispose() method.

It is important to note that when you start playing with concurrency, you...