I want to port asynchronous execution tools to Rx from the Android API. In particular, I have a photo gallery in my application, which often retrieves new photos from the server when a user views photos (based on ViewPager with side scrolling).
It happened this way: whenever the ViewPager wanted a new photo, it asked its speaker (under MVP conditions) to get it, which, in turn, went to the model. The model sent a new IntentService intent to upload a new image: 
Now it looks different: 
In the case of IntentService , if we have many requests for loading an image, these requests are queued in one IntentService and processed one at a time.
With Rx, many image download requests give a lot of Observable and possibly consume a lot of memory (I have not completed refactoring to Rx yet and, therefore, have not done any experiments, but probably someone was already thinking about it).
Am I right in my perplexity? Is there a better way to do the same with RxAndroid?
source share