Dynamic Data VS Rx.NET

Personally I learned to use rx and observables by starting to use ReactiveUI combined with DynamicData for my WPF app MVVM architecture. It was maybe not to best choice out there, but I learned to work with it and some things it allows to do is awesome.

With DynamicData you can use a ObservableCollectionExtended for your list and call .ToObservableChangeSet().WhenAnyPropertyChanged().Subscribe(t => { code to execute });

reminds a lot of https://github.com/reactivemarbles/DynamicData

If you're trying to use reactive with MVVM, you might have a look at ReactiveUI, an MVVM toolkit designed to work with reactive extensions. Specifically in this case, you could leverage DynamicData (RXUI's preferred method of handling collections), which lets you trigger updates based on change notification from child items, among other things. I'm still relatively new to RXUI myself, but if you have any questions I can certainly try to help a bit more.

Right and I never said they did. I said replace the observablecollection with an iobservable if you want it to be observable. You can then use https://github.com/reactivemarbles/DynamicData to get yourself an observablecollection. I'm not arguing that observablecollection + linq would result in an observablecollection. Just pointing out that there is a solution for this.

One of the greatest things i discovered recently, is Reactive programming / Reactive Extensions ( https://github.com/dotnet/reactive ).

https://github.com/dotnet/reactive has a lot of different time related extensions for "events". Maybe you'll find something for yourself, if you google for rate limiting with reactive.

Install Reactive Extensions: https://github.com/dotnet/reactive

Another option is to use the RxJava library in Java. This library uses reactive programming principles to make it easy to write asynchronous and event-driven code. It's particularly well-suited for handling streams of data and allows you to write code that is both efficient and easy to read.

I'd use a dedicated event bus based on Reactive Extensions or MediatR to publish domain events from your domain services. This probably doesn't solve all your ViewModel update problems as is, maybe you need to revise the granularity (maybe you can have smaller ViewModels that refresh single property that exposes the Model) and lifespan (sometimes you can create a ViewModel, make it perform it's task and then discard it completely) of your ViewModels.

If you're finding yourself in a situation where you need to turn this behavior into a pattern because there are a lot of View Models that need to execute async business logic in response to some changes, I'd go with something like MediatR or Reactive Extensions. The idea is, again, that some other, probably business-level, component listens to changes in a decoupled way (that means it doesn't subscribe directly to your View Model, but to an event bus instead). View Model publishes change events to the event bus, and business-component reacts to these events by executing the business logic.

We'd really appreciate if it consumers of the library could update and provide any issues / bugs via the GitHub repo: https://github.com/dotnet/reactive/issues