NgRx is a popular state management framework implementing the Redux standard for Angular. Nevertheless, it is often one of the hardest things to learn when you are learning Angular. Often the confusion is not in the Redux flow itself (it is quite simple actually) but more in how you actually put it into use.
As a consultant, I often work with new Angular developers that have a background in backend development. They are already experienced developers; they have learned the design patterns, clean code, and architecture but find it hard to apply in the context of Angular.
For big and complex applications, like an online bank, I recommend using NgRx for state management as that is a great way of orchestrating 50+ people working on the same repo.
Why?
- Easy traceability of state updates in the Dev Tools
- Supports a reactive architecture
- Is a well-known pattern in the whole frontend landscape
Nevertheless, there are certain mistakes that limit the usefulness of NgRx, that I tend to see over and over.
This post will show you the most common NgRx mistakes, so you can avoid making them and enjoy the efficiency, maintenance and scalability benefits you get from NgRx to it's full.
You can read the post here.
Top comments (0)