I am recently learning Angular 6 with @ngrx/store while one of the tutorial is to use @ngrx/store for state management, **however I don&#39;t understand the benefit of using @ngrx/store behind the scene.** 

For example, for a simple login and signup action, **previously by using the service(Let&#39;s call it AuthService)** we might use it to call the backend api, store &quot;userInfo&quot; or &quot;token&quot; in the AuthService, redirect user to &quot;HOME&quot; page and we can inject AuthService in any component where we need to get the userInfo by using DI, **which simply that one file AuthService handles everything**.

Now if we are using @ngrx/store, we need to define the **Action/State/Reducer/Effects/Selector** which probably need to write in 4 or 5 files to handle above action or event, then sometimes still we need to call backend api using service, **which seems much much more complicated and redundant...**

In some other scenario, *I even see some page uses @ngrx/store to store the object or list of object like grid data.*, **is that for some kind of in-memory store usage?**

So back to the question, **why are we using @ngrx/store over service registration store here in Angular project?**  I know it&#39;s for &quot;**STATE MANAGEMENT**&quot; usage, **but what exactly is the &quot;STATE MANAGEMENT&quot;? Is that something like transaction log and When do we need it? Why would we manage it on the front end?** Please feel free to share your suggestion or experience in the @ngrx/store area! 



All Ngrx Store Solutions on Gang of Coders

Total of 1 Ngrx Store Solutions

Angular 6 - Why use @ngrx/store rather than service injection