Understanding what is a reactive architecture in the context of an Android application — This 2nd part is about web components with OkHttp & Retrofit (playground project is available here).
In first part, we spotlighted what’s the idea behind a reactive architecture, and viewed fundamental basics of RxJava.
Let’s go with a common use case to understand what is a reactive API: the web client. For front developers, web services (and every remote services) should be considered as a source of problem: response handling, data validation, errors, bad connectivity, timeouts… A reactive approach can help you overcome all those problems.
Understanding what is a reactive architecture in the context of an Android application — First steps for building your android app with Reactive Streams (Kotlin inside !)
While debugging on one of my apps in production, I had to take the hand on some low level RxJava parts. Here is an opportunity to pause myself and share my understanding RxJava and its role for an Android application.
Why do we talk about reactive applications?
For a long time, I was considering the reactive manifesto as server side target only: server application has to be scalable, resilient, responsive, & based on…
The (retired) Pub(lication) for Android & Tech, focused on Development