reactive-programming

I'm trying to reorder events arriving unordered on different threads. Is it possible to create a reactive extension query that matches these marble diagrams: s1 1 2 3 4 s2 1 3 2 4 result 1 2 3 4 and... s1 1 2 3 4 s2 4 3 2 1 result 1234 That is: Only publish results in version number order. The closest I have got is using a Join to open a window each time s1 ticks and only close it when s2 arrives with the same number. Like this: var publishedEvents = events.Publish().RefCount(); publishedEvents.Join( publishedEvents.Scan(0, (i, o) => i + 1), expectedVersion => publishedEvents.Any(@event =>

I was trying to implement instant search on a database table with 10000+ records. The search starts when the text inside the search text box changes, when the search box becomes empty I want to call a different method that loads all the data. Also if the user changes the search string while results for another search are being loaded, then the loading of the those results should stop in favor of the new search. I implemented it like the following code, but I was wondering if there is a better or cleaner way to do it using Rx (Reactive Extension) operators, I feel that creating a second

Can someone explain the differences between an Observable and a ConnectableObservable? The Rx Extensions documentation is very sparse and I don't understand in what cases the ConnectableObservable is useful. This class is used in the Replay/Prune methods. Short answer: IConnectableObservable represents a pending hot observable that can be shared with multiple subscribers. Calling IConnectableObservable.Connect() causes the change to hot (subscribes to the cold source observable) Long answer: A cold observable (like Observable.Range ) replays the sequence for each subscriber. It's analagous to

Spring 5 introduces the reactive programming style for rest APIs with webflux . I'm fairly new to it myself and was wondering wether wrapping synchronous calls to a database into Flux or Mono makes sense preformence-wise? If yes, is this the way to do it: @RestController public class HomeController { private MeasurementRepository repository; public HomeController(MeasurementRepository repository){ this.repository = repository; } @GetMapping(value = "/v1/measurements") public Flux<Measurement> getMeasurements() { return Flux.fromIterable(repository.findByFromDateGreaterThanEqual(new Date

I'm developing an Android app using Clean Architecture and I'm migrating it to RxJava 2.x. I have to make some network requests to a soap service, so I defined the api interface in the domain module: public interface SiginterApi { Observable<User> login(String user, String password); ... Observable<List<Campaign>> getCampaigns(List<Long> campaignIds); } I've read that a network request should be made with " Flowable ", because of the backpressure management since it's a 'cold observable'. On the other hand, I know the result of the request will be success (with the response) or error, so I don