RxJava2。 Flowable的行为方式与Observable相同？

Question

It seems like mental overhead to use both Observable and Flowable in the same project for RXJava 2.

Say to distinguish in the interfaces that this method return Observable so there is not back-pressure this one does so it is with back-pressure support.

But in the end of the day we can just use Flowable to make things simpler?

Then:

Can I make Flowable to be faster to turn off pressure to behave same way as Observable does?

Answer 1

My answer to myself: use Flowable everywhere. For all API that exposed themselves through the Net.

My use case: I use RX Java to defining RX API to the Web and itneracting with other microservices by Net.

From my understanding, the projectreactor https://projectreactor.io/ (another rx iml) project there is even no question whether to go with backpressure or not. It is there for all Flux

Going back to RxJava2. It seems to me that in the RX Java it was decided to keep Observable for the backward compatibility purposes primary. (there is no good explanation why not)

And when it comes to HTTP I found that I need it even for smaller sets. Usually. Event if I return less than 1000 items to the client it does not mean that it can handle it at once (it can be busy doing other stuff), so I would go with backpressure.

So I do not won't to overcomplicate things / api / code, will go with Flowable everywhere until I see any of Observable.