Redux: Opinions/examples of how to do backend persistence?
I am wondering how folks using Redux are approaching their backend persistence. Particularly, are you storing the "actions" in a database or are you only storing the last known state of the application? If you are storing the actions, are you simply requesting them from the server, then replaying all of them when a given page loads? Couldn't this lead to some performance issues with a large scale app where there are lots of actions? If you are storing just the "current state", how are you actually persisting this state at any given time as actions happen on a client? Does anyone have some code