NgRx Signal Store appears minimal, but behind that simplicity is a surprisingly powerful and nuanced state management model.

This deep dive explores the Signal Store beyond the API surface. We’ll look closely at what Rx Methods are capable of: orchestration, async flows, side effects, error handling, and composition and how they differ from classic NgRx effects and service-based approaches. We’ll break down the Events Plugin, how it works internally, what problems it solves, and how it enables decoupled communication without reintroducing global state complexity.

The focus is on architectural decision-making. When should you use local signals, services, Signal Store state, Rx Methods, or Events? How do you define state boundaries, model derived state, and avoid leaking state across features? We’ll discuss common misconceptions, trade-offs, and anti-patterns, grounded in realistic real-world scenarios rather than toy examples.

By the end of the session, you’ll have a clear mental model for when and when not to use each NgRx Signal Store building block, enabling you to design scalable, maintainable Angular applications with confidence.

A deep, opinionated look at NgRx Signal Store—Rx Methods, Events, and the architectural decisions that matter when building scalable Angular applications.