redux-persist VS Rx.NET

Storage: redux-persist, @react-native-async-storage/async-storage

Next, following their official document, I added some changes to my store.

redux-persist : For persisting data locally

One thing to keep in mind with persisting data to a device is that you maybe have to run migrations on that data if your app starts to use that data differently. https://github.com/rt2zz/redux-persist/blob/master/docs/migrations.md

for most applications, AsyncStorage works fine. also, you can use it with redux-persist or persist middleware of zustand. in this way, you won't even need to touch the AsyncStorage. my first choice as a database (or just a persistor tool) is zustand and AsyncStorage. this combination can solve storage issues most of the time.

That is also admittedly not very smart. Maybe you only want to persist certain slices, maybe you need to do other things with it. That's why https://github.com/rt2zz/redux-persist and other similar addons exist.

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