Too Long; Didn't Read
State in reactive programming is data that dictacts the configuration of the application in any moment in time. In order to understand how to better manage state, we need to know how many types of state there can be. I like to classify state in two ways and then choose the technologies that are best suited for managing those kinds of state. The general rule of thumb while managing this sort of state is to see how far the components consuming it are in the component tree. Never put UI state in the cache. This is not be confused by the state that is managed between the server and the database.