The need for more intuitive, fine-grained reactivity and simplified state handling is often one of the reason why simpler solutions are sought than NGRX/Redux.
NGRX Signals and its SignalStore utility are the latest additions to the NGRX suite and aim to address these modern demands providing a simpler and lightweight solution.
And above all it's totally detached and independent from NGRX Store!
This new package simplifies state management by allowing developers to harness the power of Signals for managing component-level state while maintaining the familiar patterns and best practices of NGRX.
When to use NGRX Signals and when NGRX Store?
The answer is not simple. Both approaches are very good and suitable for dealing with more or less complex scenarios.
Some colleagues claim that NGRX Signals is simpler but, as you will see in the following pages, things can get complicated easily.
I prefer the order, discipline and separation of responsibilities provided by NGRX Store and the Redux pattern but probably because I use Redux in React for many years and it’s a pattern I love.
So, I would say that today the choice is conditioned by personal preferences and the approach that most prefer:
NGRX Store, if you are a fan of the Redux pattern
NGRX Signals if you prefer a more declarative and responsive approach