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.
Table of Contents (22 chapters)
1
Section 1: Foundations of Reactive Programming in Java
5
Section 2: Reactive Operators
12
Section 3: Integration of RxJava applications
Appendix B: Functional Types
Appendix E: Understanding Schedulers

Configuring JUnit

In this section, we will be using JUnit as our testing framework. Add the following dependency to your Maven or Gradle project.

Here is the configuration for Maven:

<dependency>
<groupId>junit</groupId>
<artifactId>junit</artifactId>
<version>4.13</version>
<scope>test</scope>
</dependency>

Here is the configuration for Gradle:

dependencies { 
compile 'junit:junit:4.12'
}

To save yourself the hassle, organize your code project to conform to the Maven standard directory layout. You might want to place your test classes in a src/test/java/ folder so that Maven and Gradle will automatically recognize it as the test code folder. You should also put your production code in a src/main/java/ folder in your project. You can read more about the Maven standard directory layout at https...