# Beyond Component State — Angular

Source: https://www.geekswithgeeks.com/en/angular/ng-state-management

> When and how to share state across the app.

## When you need more

Once two unrelated components need the same data — a logged-in user, a shopping cart — component-local state stops being enough, and you reach for a shared store.

## Options: services vs NgRx

A **root-provided service holding signals** is often enough for small-to-medium apps. Larger apps with complex, traceable state changes sometimes reach for **NgRx** — a Redux-style store with actions, reducers, and effects.

## Start simple

Reach for a full state-management library only once a shared service with signals genuinely becomes hard to reason about — it's easy to over-engineer this early.
