Your Angular application is a reactive system. It reacts to different events and updates the model, then propagates the changes through the component tree. It works like a charm for the simple and not UI-intensive apps. But when you, following this architecture, meet some more complex use cases (like concurrent data modification, complex component intercommunications, the need to keep temporary UI state, etc), it's time to think about a different way to manage the app state. Redux pattern to the rescue! But Redux in the Angular way. We have reactive forms, reactive router, observables-based HTTP-client, so let's have a look at reactive Redux called NgRx platform.

In this session: intro to the state management (famous Facebook bug), base principles and components of Redux, converting our regular app to the one using centralized store using NgRx platform, tooling, pros and cons of having a centralized store for the state management.