Why Angular Signals Will Replace RxJS for State Management

Angular Signals, introduced as stable in Angular 17, represent a fundamental shift in how we think about reactivity in Angular applications. After years of relying heavily on RxJS for state management, many teams are now asking: is it time to migrate?

What Are Signals?

Signals are a reactive primitive — a wrapper around a value that notifies consumers when that value changes. Unlike Observables, they are synchronous, always have a current value, and are much easier to debug.

The Case for Signals

For most component-level state, Signals are dramatically simpler. Consider a counter: with RxJS you need a BehaviorSubject, an Observable pipe, and an async pipe in the template. With Signals, it is a single line.

When to Keep RxJS

RxJS still wins for complex async orchestration — HTTP requests with retry logic, debounced search, combining multiple streams. The two can coexist and complement each other perfectly.

Our recommendation: use Signals for component state and simple derived values, keep RxJS for async workflows and cross-component communication.