michaelcontento / redux-storage

Persistence layer for redux with flexible backends
MIT License
675 stars 50 forks source link

[question] what are the pros and cons against redux-persist? #133

Closed sibelius closed 8 years ago

michaelcontento commented 8 years ago

I'm not following the development on redux-persist but in it early days it was somewhat monolithic. But this might have changed ...

I started with redux-storage because I needed a very lightweight and simple way to persist my redux state. All existing solutions, at that time, where either to opinionated/big or missed some features and where not flexible enough. So redux-storage became alive and I tried to keep the core (aka redux-storage) as simple/small as possible. This is why all major features (filtering, immutablejs support, debounce / batch save operations or different engine e.g. react-native) are separate projects.

So if you want a small core and the ability to extend every aspect - redux-storage should be a good fit 😎 Here a short overview of modules that can be used to configure different aspects of redux-storage:

I'll go ahead and close this issue to keep the list of open issues as short as possible. But feel free to re-open this issue if something is unclear or you simply want to discuss this further 😄