Reactive Programming on Android with RxJava_468 x 60 copy 2.png

tarball.tar.gz

RxJava

Since its inception in 2012, RxJava has slowly gained in popularity for enabling reactive programming on Android. It is now deemed as the go-to and leading reactive library. Many companies have adopted the reactive way of programming, including Google, with its release of Android Architecture Components, which has many reactive elements in its design.

In this course, you will learn the fundamental principles of RxJava which will serve as a foundation for experienced Android developers who are new to the library and want to start integrating it into their apps.

Reactive Programming with RxJava

## Issue: Violation of RxJava's Laziness
RxJava is designed with laziness in mind. Revisit Lazy Emissions]for a reminder. That is, no long operations should be performed when there are no subscribers to the `Observable`. With this modification, that assumption is no longer true since `UserCache.getAllUsers()` is invoked even before there are any subscribers. Whether or not the backing cache is in memory or on disk, this operation should be postponed until an `Observer` subscribes to it, to stay true to RxJava principles.


# Issue: Violation of RxJava's Laziness
RxJava is designed with laziness in mind. Revisit Lazy Emissions]for a reminder. That is, no long operations should be performed when there are no subscribers to the `Observable`. With this modification, that assumption is no longer true since `UserCache.getAllUsers()` is invoked even before there are any subscribers. Whether or not the backing cache is in memory or on disk, this operation should be postponed until an `Observer` subscribes to it, to stay true to RxJava principles.


Let's address the issue of the violation of RxJava's laziness principle.

Getting Started

Part 1: RxJava Basics

Reactive Programming

RxJava Core Components

Operators

Multithreading

Part 2: RxJava Advanced

Reactive Modeling on Android

Backpressure

Error Handling

Conclusion

RxJava's Consequences: Laziness

Issue: Violation of RxJava’s Laziness