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

Introducing lambda expressions


Java officially supported lambda expressions when Java 8 was released in 2014. Lambda expressions are shorthand implementations for single abstract method (SAM) classes. In other words, they are quick ways to pass functional arguments instead of anonymous classes.

Making a Runnable a lambda

Prior to Java 8, you might have leveraged anonymous classes to implement interfaces, such as Runnable, on the fly as shown in the following code snippet:

public class Launcher {

    public static void main(String[] args) {

        Runnable runnable = new Runnable() {
            @Override
            public void run() {
                System.out.println("run() was called!");
            }
        };

        runnable.run();
    }
}

The output is as follows:

run() was called!

To implement Runnable without declaring an explicit class, you had to implement its run() abstract method in a block immediately after the constructor. This created a lot of boilerplate and became a major...