RxRelay VS RxJava

BehaviorRelay is really good

RxJava with RxRelay (and rx-combinetuple-kt)

Spoilers is that I just store every variable in their own BehaviorRelay.

interesting approach; are you referring to the RxRelay library? do you exclusively use that/RxJava APIs for async work/reactivity in the business domain/data layers as well?

Although generally, just don't use subjects ever, use https://github.com/JakeWharton/RxRelay instead

RxRelay + Rx-CombineTuple-Kt (+ Rx-ValidateBy-Kt) are things I use in my everyday life

3. RxJava This repository contains the source code for ReactiveX, a library used to create asynchronous and event-based programs with observable sequences. https://github.com/ReactiveX/RxJava

Is this similar RxJava, the reactive extensions library for https://github.com/ReactiveX/RxJava ? I have made that work in Clojure in production.

Since you mentioned java, there is RxJava and RxAndroid. Google general recommendation now is to use kotlin coroutines if you're considering writing your app with that.

It's very quick though. In terms of the correctness of the syntax, I've never seen an issue while translating a single file or a single function. When I took the entire RxJava code base 5 years ago, right clicked on the source folder and converted to Kotlin, I found lots of problems. File by file I've never seen any issues though, but I also haven't done it much.

You all beat me to MapStruct and Testcontainers. Honorable mention to RxJava, which I use in Desktop apps.

RxJava with RxRelay (and rx-combinetuple-kt)

RxJava2

More information about rxJava, check it out here: (HERE)[https://github.com/ReactiveX/RxJava]

Concurrency: Kotlin coroutines for general use, Rx or Flow for reactive programming (you can technically use Rx for regular concurrency as well, but not really what it's meant for)

If you're just looking at making a service call on a regular interval and notifying the user when there's an actual change in data, you can also look into RxJava https://github.com/ReactiveX/RxJava. From here you can "subscribe" to your service call, and then every time you make your service call you can have it look for changes compared to the previous emission .distinctUntilChanged() and then only notify it's subscribers when it notices an actual change. From there you can trigger a local notification and push to a LiveData (assuming MVVM) or otherwise update the UI to match as well.