Simple state management in Angular with only Services and RxJS

Aslan Vatsaev on February 10, 2019

One of the most challenging things in software development is state management. Currently there are several state management libraries for Angula... [Read Full]
markdown guide
 

Definitely my preference. Generally the applications I find myself building don't need anything more than this, and pure observable contexts make things so much more composable, no magic strings anywhere.

 

Exactly what I'm trying to do in my app. An advice: don't put HTTP, async services, etc. into the store. Keep it separate. State management has nothing to do with such services and business logic. Ngrx Effects is a terrible mix of two concepts.

 

You're right, side effects must always be separated from state management, this was a quick example, i'll try to clean it up when I have some free time.

 

Honestly, unless your app is extremely complicated, anyone using a state management library for Angular has misunderstood the component life cycle and is pretty much trying to make Angular into a React application.

 

This looks really nice. After 4ish projects across React and Angular, I have yet to find the Redux pattern remotely worth it... But I'll say that has a lot to do with particular executions...

Regardless, this seems like this would make life a lot easier. :)

One question, tho: is the shareReplay in completedTodos$ not redundant? It would call shareReplay twice in a row in the pipe.

 

To be honest I'm not sure, I've put it for good measure, but theoretically yes, i didn't have to use shareReplay on filtering considering that the original source is already multicast, I'll do some tests to confirm, and remove it later.

 

This is exactly what I do in my project. I trialled ngrx/store but found it so overly bloated with a ridiculous amount of boilerplate for very little gain. This pattern is simple, elegant, easy to reason about.

 

I notice that the StackBlitz project refers to an undefined trackBy function:

todosTrackFn

I can't see any problem that it is causing. The project compiles ok. TSLint flags the problem in my vscode edit buffer.

 
 

Accessors for the same member name must specify the same accessibility

todos getter/setters must either both be public or both be private. My preference is they are private, so that publicly, only the observable is accessible.

Another alternative is make private set _todos and public get todos.

You probably already know better than me which options are best, but thought I throw some options out there for others that come across this.

Thanks for the excellent example. Do you by any chance have an example for todosGroup and todos, and how they would work with each other when navigating from group to single todo?

Thank you for sharing. I value your input as a developer and person. :D

 

I've almost made a career out of reducing the complexity and size of Angular 2+ apps by appropriately using services and RxJs instead of convoluted, home-grown solutions to state management.

My resume:

  • Read the Angular docs past the 2nd page.
 

why use behavior subject with sharereplay?
get todos() is also overkill. It's not a good way to get data from observer, except in async pipe. For adding todo we should use scan operator, same as for mark as completed. Subject with shareReplay (or ReplaySubject) solves all the problems and BehaviorSubject is really redundant here.

 
 

Whats your opinion about using this method in a complex application that doesn't use any state management at all yet (due to lack of initial planning), but our team would like to change this in the future regarding modules one by one starting with the most complex one. Is it a good idea to go with this one, or would it be better idea to go with ngrx because of the complexity?

 

Depends on the scale, if you have a big app with a lot of components than need to share state, and a lot of moving parts, i strongly suggest ngrx, i used this method (the one described in the article) to build several libraries that have internal state, and it works very well, so no need to use ngrx in component libs.

 

If you are reaching this level of complexity with more than 1-2 services then i would suggest start looking into using a library with some more restraints.

At least if you are more than 1-2 devs touching the codebase.

Otherwise long-term feature additions and bugfixes are likely to turn this into state soup eventually, once developers start to slack a bit or implement newer idea's.

Which is bound to happen sooner or later in a system without opinionated restraints.

I liked the demo service example, but would have liked to see some with less observable bootstrapping, and maybe just some general guidelines.

Since that's what i find smaller projects benefit more from in my experience. :)

Found the article a good read however, thanks!

 

This was my thought as well.

From looking around it seems like (as of today) Akita basically is this approach, plus some organizational patterns/practices that should help encourage consistency.

I do wish there was a library out there with a longer track record that was lighter than NGRX.

 

First of all, thanks for the article.
Its really great, and certainly expanded my horizons on the use of RxJS.

Just one question, on stack blitz you use toPromise() on the calls to the rest api. This could not also be achieved using observables?

this.todosService.setCompleted(id, isCompleted)
.pipe(take(1))
.subscribe({
next: value => {},
error: err => {
console.error(e);
this.todos[index] = {
...todo,
isCompleted: !isCompleted
}
}
});

I did see that you use it because of async/wait but not understand why.
I'm just trying to understand the difference between the two approaches.

Thanks!

 

Absolutely brilliant! Always know your actual toolset before buying into new ones!

 

Hey Aslan, I do the same thing, except I don't understand the need for sharedReplay. You're already sharing the same observable because it's assigned to a public readonly property. And you're also using a BehaviourSubject which should always return the current value to new subscribers. Also, why not just use a ReplaySubject if you need the previous value? You lose getValue, but it's not such a big deal because you probably want to subscribe anyway. What am I missing?

 

BehaviourSubject is not a simple observable, it's an observer AND an observable at the same time that can give you its latest state synchronously.

You're already sharing the same observable because it's assigned to a public readonly property

That doesn't mean the observer is shared, and that doesn't change the fact that when someone subscribes to todos$, a new dedicated observer will be created for it. A shared observable means that all subscribers are getting their data stream from a single observable source. (lookup rxjs multicasting)

More info here: learnrxjs.io/operators/multicastin...

Also, why not just use a ReplaySubject if you need the previous value? You lose getValue...

I need to be able to get the previous state synchronously in the reducers, as I already explained in my other comment, reducers are synchronous functions that take previous state and reduce it to a new state in an immutable way.

The reason we need the replay part is because some components might be rendered asynchronously (after fetching some data from api for ex), and might miss the emits in todos$ observable, so when they subscribe to it they won't know what happened in the source before component came to life, the replay will emit the latest value to all observers upon subscription.

On the other hand, the second share replay is not necessary, I updated the code.

Hope I answered your questions.

 

Thanks for this. Have been exploring NgRx and have been feeling "this isn't worth it". Did a google search for "simple Angular state management" and here I am.

 

"this isn't worth it"

depends on the case, when I work on large scale apps with a lot of moving parts, it's very worth it

 

How do you organize your stores files on the project structure? Do you keep in a separate folder or within the component itself? Thanks!

 

separate modules for each store, inside the module: reducers, effects, facades.

 

Great article. Thank you.
I'm trying to adapt this kind of state managment to my app.
In my scenario I'm subscribing to some events (adding, removing) and do some other logic (for example showing message "you have removed something").
How would you modify your todo example to add this kind of logic in a separate file/ or in other components?

 

What difference is there in using BehaviorSubject in a state manager class instead of sharing a service class with properties passed by reference?

 

onPush change detection, combining/manipulating data streams with RxJS, and it's really fast.

 
 

I really liked this approach and I'm definitively going to use it! But I wonder how could it be used when we actually have to fetch data from an API?

 
 

Aslan, I like this approach quite a bit, but I have the same questions. What would it look like when fetching data from an API?

Hey @klouddy @gabrielaraujof , I've updated the stackblitz example with a real REST API and some interesting techniques on how to do optimistic updates and rollbacks: stackblitz.com/edit/angular-rxjs-s...

 

I've updated the stackblitz example with a rest api

 

Shouldn't the getter and setter for todos be private as well?

 
 
 

Useful and clean implementation of a simple state management.

 

Thanks for sharing, this is exactly Im looking for.

 

I notice that the StackBlitz project differs from your article somewhat. In particular, you convert observables to promises in several places. Can you explain why you do that? Thanks

 

I convert them to Promises so I can use async/await

 

Awesome post, do you have any ideas to better handle business logic and reactive forms? I find it's not that easy to make them well decoupled.

 

What do you think about using Subjects as observables in your app state service, I find the very convenient.

 

If possible, it would be great if you could update the article to match the StackBlitz code. Thanks

 

I'd like to keep the article as simple and lightweight as possible, and i commented the code on stackblitz, but if anything isn't clear enough feel free to ask

code of conduct - report abuse