{"id":1493,"date":"2023-09-22T05:00:00","date_gmt":"2023-09-22T12:00:00","guid":{"rendered":"https:\/\/www.angulartraining.com\/daily-newsletter\/?p=1493"},"modified":"2023-09-19T14:10:35","modified_gmt":"2023-09-19T21:10:35","slug":"introduction-to-state-management","status":"publish","type":"post","link":"https:\/\/www.angulartraining.com\/daily-newsletter\/introduction-to-state-management\/","title":{"rendered":"Introduction to State Management"},"content":{"rendered":"\n

When you work with Angular for quite some time, you realize that you implement similar services repeatedly. Most likely, you end up with services with BehaviorSubjects<\/a> to store some data, and you have components that subscribe to these subjects exposed as read-only Observables<\/a>.<\/p>\n\n\n\n

If you’re not at that point yet, I suggest you stop reading this article and get into the above architecture pattern first. This is a good reading<\/a> about what I call “progressive state management<\/a>,” where you get into state management little by little. Start there.<\/p>\n\n\n\n

Once comfortable with the above, you might start thinking about NgRx<\/a>, NgXs<\/a>, or other state management libraries.<\/p>\n\n\n\n

Why state management?<\/h3>\n\n\n\n

The main goal of a state management library is to define a single way to handle data<\/strong> in your application. Instead of having your application data in multiple different services, all your data will belong in a single, massive object called state<\/strong>. That state has to follow several rules and cannot be updated directly. <\/p>\n\n\n\n

State management is all about rules and conventions created by the ancestor of all state management libraries: Redux<\/a>. All modern libraries use similar concepts and vocabulary.<\/p>\n\n\n\n

Here are the three core principles of Redux<\/strong>:<\/p>\n\n\n\n