RxJava 2远程请求失败后获取本地数据的最优实现方案问询

Hey there! Let's tackle this problem of falling back to local data when a remote request fails using RxJava. I totally get where you're coming from with that initial approach—it's the first thing most folks reach for when starting out, but it does have some drawbacks.

First, let's break down the beginner-style approach you mentioned:

最先想到的简易写法如下：

val remote = remotePurchase.getAvailableUsersMaxCount()
    .subscribe({
        // 处理远程请求成功的结果
    }, {
        // 请求失败时调用getLocal()
    })

This nested callback pattern is super common for RxJava newcomers, but it quickly gets messy. It breaks the reactive chain, makes the code harder to read, and adding extra logic (like retries or error logging) will just bloat the callback even more—totally not leveraging RxJava's full potential.

The best way to handle this "remote first, local fallback" flow is using the onErrorResumeNext operator. It's built exactly for this scenario: when the source Observable throws an error, it switches to a fallback Observable seamlessly.

Here's how you can implement it properly:

override fun getActualUsersMaxCount(): Observable<Int> {
    return remotePurchase.getAvailableUsersMaxCount()
        // When remote request fails, switch to local data
        .onErrorResumeNext { throwable ->
            // Optional: Log the error for debugging
            Log.d("UserCountRepo", "Remote request failed: ${throwable.message}")
            // Return the local data Observable as the fallback
            getLocalUsersMaxCount()
        }
}

// Example local data fetch function (adjust to your actual local storage)
private fun getLocalUsersMaxCount(): Observable<Int> {
    // Could be from SharedPreferences, Room DB, or a local file
    return Observable.just(100) // Replace with your real local data logic
}

Why this works better: #

• No nested callbacks: The code stays in a clean, readable reactive chain
• Separation of concerns: Error handling and fallback logic are neatly integrated without cluttering your success handler
• Easy extensibility: Want to retry the remote request a couple times before falling back? Just add retry(2) right before onErrorResumeNext
• Granular error control: If you only want to fallback on specific errors (like network failures), you can add a check:

  .onErrorResumeNext { throwable ->
      if (throwable is IOException) {
          // Only fallback on network errors
          getLocalUsersMaxCount()
      } else {
          // Re-throw other errors to let upstream handle them
          Observable.error(throwable)
      }
  }
  

内容的提问来源于stack exchange，提问作者Serg Burlaka