platform VS mobx-state-tree

NgRx is the standard library for state management in Angular applications. With NgRx v14, many of the complex APIs following the Redux pattern have been greatly simplified. For example, ActionGroups make it easier to define new actions. However, the use of the Redux pattern is by no means easy and discourages many developers.

I ran into this question question on the NgRx GitHub discussion threads which asked:

In an application that I’m working on, before Angular 16 shipped, I was using a custom StoreService to hold global application state. I’ve tried libraries like NgRx and Akita to manage global state, but found them to be way too heavy-handed for what I wanted (not saying ANYTHING negative towards these libraries; not every tool is right for every job, and the authors of these libraries would probably be the first to tell you that). This custom StoreService was created using RxJS, and looked like this:

RFC Signal Store

If you liked this, click the ❤️ so other people will see it. Follow me on Twitter and subscribe to my YouTube Channel for content on Angular, Analog, NgRx, and more!

The store can be implemented using any technology. You can either use a library like NgRx or NGXS. Another solution is to create your own store using a BehaviorSubject.

I'm using @ngrx/router-store in my Angularv5 app and I recently started running into a an error: Navigation ID X is not equal to the current navigation id Y (where X and Y are integers).

Not agree, NgRx and redux pattern helps a lot to keep the code clean, I do agree that maybe NgRx add many files and could become in boilperplate for simple staff, I think with signals this approach will change, there is already an open discussion about this https://github.com/ngrx/platform/discussions/3796

For code sample and how to architect these things : https://ngrx.io

The NgRx team and Marko Stanimirović opened a new RFC (Request for Comments) for a signal-based state management solution, SignalStore. It has a similar approach to @ngrx/component-store. The initial prototype with the API documentation is available in the NgRx SignalStore playground repo.

Basic knowledge of Tailwind CSS and MobX-State-Tree

Folks disagreed with my comment yesterday criticizing Redux as an architecture, but this sort of illustrates my point. I'd suggest taking a look at Mobx State Tree, which automatically re-renders components only when they depend on the specific part of the state that changed. Other fields can change without triggering unnecessary re-renders, and developers don't have to worry about manually splitting the state to deal with performance problems.

mobx-state-tree (https://mobx-state-tree.js.org/)

Benefits of it over mobx is data normalization with references and JSON patches which allow you sync complex state easily. Typed models are also a plus.

Drawbacks are performance (see https://github.com/mobxjs/mobx-state-tree/issues/1267).

Previously was using immer, which I loved because of immutability but moved off since classes and OOP didn't feel as natural as in mst.

If I were to pick an alternative, might try redux with normalization https://redux.js.org/usage/structuring-reducers/normalizing-....

And if I were to build a state management tool, I would prioritize a library that has

MobX - or even MobX-state-tree if you prefer

As for state imba doesn't impose any paradigm on you - you are free to bring your own state managment. So you could use a library like mobx-state-tree.

We have covered almost all required topics from MobeX-State-Tree. MobeX provided few sample example, download ToDoMVC - app using React and MST and Bookshop - app with references, identifiers, routing, testing etc.

MobX-State-Tree -> MobX is a state management "engine", and MobX-State-Tree gives it structure and common tools you need for your app.

Recoil is cool, I would also recommend mobx-state-tree which is not much more complex to use and gives you nice type safety and reactivity. You can easily get a snapshot of the whole store and restore from it.