Angular › State Management

How do you decide between using a simple signal based service, NgRx, or Angular's built in state features for a specific project?

Advanced

Answer

A simple signal based service works well for most small to medium apps, especially with straightforward shared state. NgRx becomes valuable for very large apps with complex, frequently changing shared state across many features, or when a large team needs the strict predictability and tooling that NgRx provides, such as time travel debugging.

// Simple case, a signal based service is enough
@Injectable({ providedIn: 'root' })
export class ThemeService {
  theme = signal('light');
}

// Complex, frequently changing global data, NgRx may fit better
this.store.dispatch(loadDashboardData());

Real-world example A small team app manages its theme preference using a simple signal based service, since it rarely changes, but adopts NgRx for their frequently updating real time order tracking data, since that data's complexity justified the added structure.

Common follow-ups: What specific signs suggest a project has outgrown a simple service based approach?;How easy is it to migrate from a simple approach to NgRx later if the app grows significantly?

NgRx State Management;Angular Style Guide & Best Practices