--- title: A Guide to State Management in Angular for Beginners description: State management in Angular follows a ladder of four levels, from component state to NgRx SignalStore. Using a shopping cart example, it shows when a single... canonical: https://daily.dev/posts/a-guide-to-state-management-in-angular-for-beginners-hvbg57tal twitter:card: summary_large_image twitter:site: @dailydotdev og:type: website og:site_name: daily.dev og:title: A Guide to State Management in Angular for Beginners | daily.dev og:description: State management in Angular follows a ladder of four levels, from component state to NgRx SignalStore. Using a shopping cart example, it shows when a single... og:url: https://daily.dev/posts/a-guide-to-state-management-in-angular-for-beginners-hvbg57tal og:image: https://api.daily.dev/og/posts/hvBG57TAl.png og:image:alt: A Guide to State Management in Angular for Beginners og:image:width: 1200 og:image:height: 630 og:locale: en --- > ## Documentation Index > Fetch the complete documentation index at: https://daily.dev/llms.txt > Use this file to discover all available pages before exploring further. # A Guide to State Management in Angular for Beginners **[Angular.love](https://daily.dev/sources/angularlove)** · 14 min read · 0 upvotes · 0 comments ## Summary State management in Angular follows a ladder of four levels, from component state to NgRx SignalStore. Using a shopping cart example, it shows when a single component's signal suffices, when to move shared data into a service with BehaviorSubject, when to structure that service as a store with initial state, selectors and a single update function, and when to adopt classic NgRx Store with actions, reducers and effects. NgRx SignalStore (Angular 16+) gathers state, computed selectors and methods in one place using withState, withComputed and withMethods. For new projects it recommends starting with SignalStore since it adds almost no overhead over a hand-written service. It also mentions alternatives: NGXS, Elf, and TanStack Query for Angular for server state. ## Full article daily.dev links to this article rather than hosting it. Read it at the original source: ## Questions this post answers ### When should I use a BehaviorSubject instead of a plain Subject for Angular state? Use BehaviorSubject because it stores the last emitted value and delivers it immediately to new subscribers, requiring an initial value (such as an empty array). A plain Subject does not store the last value, so a component that subscribes after the last emission would show a gap in displayed state until the next change. _Developers weighing RxJS patterns for shared Angular state can find implementation examples like this on daily.dev._ ### What is the difference between classic NgRx Store and NgRx SignalStore? Classic NgRx Store (@ngrx/store) follows the Redux pattern with actions, reducers, selectors, and separate effects for async work, giving predictability at the cost of more code. NgRx SignalStore, built on signals (Angular 16+), achieves the same result without actions or scattered files by combining state, computed selectors (withComputed), and update methods (withMethods) in one place. _Teams deciding between NgRx Store and SignalStore for a new Angular app can track comparisons like this on daily.dev._ ### What are the three core elements every Angular state store should have? Every state store needs an initial state so you know the starting point, selectors so components read only the data they need with derived values computed in one place, and a single update function (like a patch method) so every state change goes through the same place for easier debugging and logging. This pattern underlies simple services, NgRx Store, and SignalStore alike. _Developers structuring their own Angular stores can revisit core patterns like this on daily.dev._ ## Similar posts on daily.dev - [Practical Guide: State Management Angular Services \+ Signals](https://daily.dev/posts/practical-guide-state-management-angular-services-signals-jt69hvsp1) · Telerik · 0 upvotes · 0 comments - [Angular 22 State Management: Signals, SignalStore, or NgRx?](https://daily.dev/posts/angular-22-state-management-signals-signalstore-or-ngrx--8kuf41mki) · We Are .NET · 2 upvotes · 0 comments - [Angular State Management: From Local Signals to NgRx SignalStore](https://daily.dev/posts/angular-state-management-from-local-signals-to-ngrx-signalstore-pcbicfvwj) · Telerik · 0 upvotes · 0 comments - [Angular NgRx: An Overview](https://daily.dev/posts/angular-ngrx-an-overview-wc5ufngir) · Atomic Spin · 0 upvotes · 0 comments - [Decision Guide for Angular State Management](https://daily.dev/posts/decision-guide-for-angular-state-management-q9rebumpn) · Telerik · 1 upvotes · 0 comments --- Tags: [#typescript](https://daily.dev/tags/typescript), [#angular](https://daily.dev/tags/angular), [#rxjs](https://daily.dev/tags/rxjs) [View this post on daily.dev](https://daily.dev/posts/a-guide-to-state-management-in-angular-for-beginners-hvbg57tal) ```json {"@context":"https://schema.org","@graph":[{"@type":"Organization","@id":"https://daily.dev/#organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180},"sameAs":["https://twitter.com/dailydotdev","https://github.com/dailydotdev","https://www.linkedin.com/company/daily-dev-ltd"]},{"@type":"WebSite","@id":"https://daily.dev/#website","url":"https://daily.dev","name":"daily.dev","publisher":{"@id":"https://daily.dev/#organization"},"potentialAction":{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https://daily.dev/search?q={search_term_string}"},"query-input":"required name=search_term_string"}}]} {"@context":"https://schema.org","@type":"TechArticle","headline":"A Guide to State Management in Angular for Beginners","url":"https://daily.dev/posts/a-guide-to-state-management-in-angular-for-beginners-hvbg57tal","mainEntityOfPage":{"@type":"WebPage","@id":"https://daily.dev/posts/a-guide-to-state-management-in-angular-for-beginners-hvbg57tal"},"datePublished":"2026-10-28T11:37:07.078Z","dateModified":"2026-10-28T15:02:00.021Z","description":"State management in Angular follows a ladder of four levels, from component state to NgRx SignalStore. Using a shopping cart example, it shows when a single...","image":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/eaab5bad42cb796a6c6485322bfcf629?_a=AQAEuop","thumbnailUrl":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/eaab5bad42cb796a6c6485322bfcf629?_a=AQAEuop","isAccessibleForFree":true,"articleSection":"Angular.love","inLanguage":"en","publisher":{"@type":"Organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180}},"author":{"@type":"Organization","name":"Angular.love","logo":"https://media.daily.dev/image/upload/t_logo,f_auto/v1/logos/b638946cd9c74bf6a260e4e6a40212d7","url":"https://daily.dev/sources/angularlove"},"commentCount":0,"discussionUrl":"https://daily.dev/posts/a-guide-to-state-management-in-angular-for-beginners-hvbg57tal","interactionStatistic":[{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":0},{"@type":"InteractionCounter","interactionType":{"@type":"CommentAction"},"userInteractionCount":0}],"keywords":"typescript,angular,rxjs","timeRequired":"PT14M"} {"@context":"https://schema.org","@type":"BreadcrumbList","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https://daily.dev"},{"@type":"ListItem","position":2,"name":"Angular.love","item":"https://daily.dev/sources/angularlove"},{"@type":"ListItem","position":3,"name":"A Guide to State Management in Angular for Beginners"}]} {"@context":"https://schema.org","@type":"FAQPage","@id":"https://daily.dev/posts/a-guide-to-state-management-in-angular-for-beginners-hvbg57tal#faq","mainEntity":[{"@type":"Question","name":"When should I use a BehaviorSubject instead of a plain Subject for Angular state?","acceptedAnswer":{"@type":"Answer","text":"Use BehaviorSubject because it stores the last emitted value and delivers it immediately to new subscribers, requiring an initial value (such as an empty array). A plain Subject does not store the last value, so a component that subscribes after the last emission would show a gap in displayed state until the next change. Developers weighing RxJS patterns for shared Angular state can find implementation examples like this on daily.dev."}},{"@type":"Question","name":"What is the difference between classic NgRx Store and NgRx SignalStore?","acceptedAnswer":{"@type":"Answer","text":"Classic NgRx Store (@ngrx/store) follows the Redux pattern with actions, reducers, selectors, and separate effects for async work, giving predictability at the cost of more code. NgRx SignalStore, built on signals (Angular 16+), achieves the same result without actions or scattered files by combining state, computed selectors (withComputed), and update methods (withMethods) in one place. Teams deciding between NgRx Store and SignalStore for a new Angular app can track comparisons like this on daily.dev."}},{"@type":"Question","name":"What are the three core elements every Angular state store should have?","acceptedAnswer":{"@type":"Answer","text":"Every state store needs an initial state so you know the starting point, selectors so components read only the data they need with derived values computed in one place, and a single update function (like a patch method) so every state change goes through the same place for easier debugging and logging. This pattern underlies simple services, NgRx Store, and SignalStore alike. Developers structuring their own Angular stores can revisit core patterns like this on daily.dev."}}]} ```