Apache Ignite VS Redux Persist

Ignite works as you describe: https://ignite.apache.org/ I wouldn't really recommend this approach, I would think more in terms of subscriptions and topics and less of a 'database'. - Source: Hacker News / about 2 years ago

Last days, I started using Apache Ignite as a cache strategy for some applications. Apache Ignite is an open-source In-Memory Data Grid, distributed database, caching, and high-performance computing platform. Source: over 2 years ago

Storage: redux-persist, @react-native-async-storage/async-storage. - Source: dev.to / 3 months ago

Next, following their official document, I added some changes to my store. - Source: dev.to / 10 months ago

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. - Source: dev.to / over 1 year ago

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. Source: over 1 year ago

On a side note, can I suggest using library like redux or better redux toolkit (with react-redux) to manage the cart? You can then dispatch actions to update the store (cart) and use redux-persist to update the localStorage automatically. Source: almost 2 years ago