You Don’t Need NgRx Anymore — Or Do You?

For years, NgRx was the go-to solution for state management in Angular. Actions. Reducers. Effects. Selectors. It brought structure, predictability, and scalability. But Angular has changed. With Signals, simpler services, and better reactivity, many developers are asking: Do we still need NgRx? The answer isn’t a simple yes or no. 🚀 Why NgRx Was So Popular NgRx solved real problems: Centralized state Predictable data flow Debugging with DevTools Great for large, complex apps For enterprise-scale applications, this structure was a lifesaver. ⚡ What Changed in Angular Modern Angular introduced: Signals (signal, computed, effect) Better component-level state Cleaner reactivity without heavy RxJS Example without NgRx: @ Injectable () export class UserStore { private users = signal < User [] > ([]); activeUsers = computed (() => this . users (). filter ( u => u . active ) ); setUsers ( data : User []) { this . users . set ( data ); } } No reducers. No actions. No boilerplate. Just state +