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.

Related Content you might be interested in

Current Title:

Small book image
Learning RxJava - Second Edition
Nick Samoylov | Thomas Nield
Feb, 2020 | 412 pages
Small book image
Reactive Programming in Kotlin
Rivu Chakraborty
Dec, 2017 | 322 pages
Small book image
Reactive Android Programming
Tadas Subonis
May, 2017 | 256 pages
Small book image
Reactive Programming With Java 9
Tejaswini Mandar Jog
Sep, 2017 | 402 pages
Table of Contents (22 chapters)
Preface
Preface
Who this book is for
What this book covers
To get the most out of this book
Get in touch
1
Section 1: Foundations of Reactive Programming in Java
Section 1: Foundations of Reactive Programming in Java
Free Chapter
2
Thinking Reactively
Thinking Reactively
A brief history of ReactiveX and RxJava
Thinking reactively
Why should I learn RxJava?
Setting up
A brief exposure to RxJava
RxJava 1.x, 2.x, or 3.0 – which one do I use?
When to use RxJava
Summary
3
Observable and Observer
Observable and Observer
The Observable
The Observer interface
Cold versus hot observables
Other Observable sources
Single, Completable, and Maybe
Disposing
Summary
4
Basic Operators
Basic Operators
Conditional operators
Suppressing operators
Transforming operators
Reducing operators
Collection operators
Error recovery operators
Action operators
Utility operators
Summary
5
Section 2: Reactive Operators
Section 2: Reactive Operators
6
Combining Observables
Combining Observables
Merging factories and operators
Concatenating factories and operators
Ambiguous operators
Zipping operators
Combining the latest operators
Grouping operators
Summary
7
Multicasting, Replaying, and Caching
Multicasting, Replaying, and Caching
Understanding multicasting
Automatic connection
Replaying and caching
Subjects
Summary
8
Concurrency and Parallelization
Concurrency and Parallelization
Why concurrency is necessary
Concurrency in a nutshell
Introducing RxJava concurrency
Understanding schedulers
Understanding subscribeOn()
Understanding observeOn()
Parallelization
Understanding unsubscribeOn()
Summary
9
Switching, Throttling, Windowing, and Buffering
Switching, Throttling, Windowing, and Buffering
Buffering
Windowing
Throttling
Switching
Grouping keystrokes
Summary
10
Flowable and Backpressure
Flowable and Backpressure
Understanding backpressure
Understanding Flowable and Subscriber
Creating Flowable
Using onBackpressureXXX() operators
Using Flowable.generate()
Summary
11
Transformers and Custom Operators
Transformers and Custom Operators
Composing new operators from existing ones using compose() and transformers
Using the to() operator for fluent conversion
Creating new operators from scratch using lift()
Creating a new operator for Single, Maybe, or Completable
Using RxJava2-Extras and RxJava2Extensions
Summary
12
Section 3: Integration of RxJava applications
Section 3: Integration of RxJava applications
13
Testing and Debugging
Testing and Debugging
Configuring JUnit
Blocking subscribers
Blocking operators
Using TestObserver and TestSubscriber
Manipulating time with TestScheduler
Debugging RxJava code
Summary
14
RxJava on Android
RxJava on Android
Creating an Android project
Using RxJava and RxAndroid
Summary
15
Using RxJava for Kotlin
Using RxJava for Kotlin
Why Kotlin?
Configuring Kotlin
Kotlin basics
Extension operators
Using RxKotlin
Dealing with SAM ambiguity
Using let() and apply()
Tuple and data classes
The future of ReactiveX and Kotlin
Summary
16
Other Books You May Enjoy
Other Books You May Enjoy
Leave a review - let other readers know what you think
Appendix A: Introducing Lambda Expressions
Appendix A: Introducing Lambda Expressions
Introducing lambda expressions
Appendix B: Functional Types
Appendix B: Functional Types
Functional types
Appendix C: Mixing Object-Oriented and Reactive Programming
Appendix C: Mixing Object-Oriented and Reactive Programming
Mixing object-oriented and reactive programming
Appendix D: Materializing and Dematerializing
Appendix D: Materializing and Dematerializing
Materializing and dematerializing
Appendix E: Understanding Schedulers
Appendix E: Understanding Schedulers
Understanding Schedulers

Debugging RxJava code

RxJava is not easy to debug at first glance, primarily due to the lack of debugging tools and the large stack traces it can produce. Attempts are underway to create effective debugging tools for RxJava, most notably the Frodo library for Android (https://github.com/android10/frodo). We will not cover any debugging tools for RxJava as nothing has been standardized quite yet, but we will learn about an effective approach that you can take to debug reactive code.

A common theme in debugging RxJava operations is finding the bad link or the operator in the Observable/Flowable chain that is causing the problem. Whether an error is being emitted, onComplete() is never being called, or an Observable is unexpectedly empty, you often have to start at the beginning of the chain at the source and then validate each step downstream until you find the one not working correctly...

Previous Section
End of Section 7
Next Section