DEV Community

Discussion on: Why Choose NgRx?

Collapse
 
layzee profile image
Lars Gyrup Brink Nielsen • Edited

Systemate A/S. We suggested NgRx Store and Effects for a customer project with frequent background updates for many different data types as well as a few, but critical state updates from the client-side. NgRx is well-maintained by a trustworthy team, it has been around for a long time, it has good documentation, there are many learning resources available and a big community. This makes it relatively easy to onboard new developers and teams to state management in the project. It also gives reasonable trust that this framework will be around for a while which is important for a project with an expected lifetime of 5-10 years. NgRx Effects gives us a pattern for separating glue code from the rest of the application. The customer was easily convinced that NgRx was a good choice.

Collapse
 
wesgrimes profile image
Wes

Thanks Lars! I agree on all accounts.