Systems | Development | Analytics | API | Testing

In part one of this series, we explored how Angular Signals shift the reactive model away from the RxJS-centric approach we’ve relied on for years. We walked through the core API signal(), computed(), and effect() primitives, and demonstrated how they simplify state management by removing the need for subscriptions, teardown logic, and deeply nested observables. We also introduced a minimalist CartService that held cart items in a private signal and exposed a computed total price.

In the world of Angular, reactivity has long been synonymous with RxJS. For years, developers have used observables, operators, and async pipes to build dynamic, reactive applications. But while powerful, RxJS brings a steep learning curve and often requires more mental juggling than necessary. Angular Signals change that. They introduce a new reactivity model that is intuitive, precise, and designed for clarity.