Kind of a full-stack software development which mostly works with front end development. Always trying to produce good structured, reliable, tested and maintainable code.
I've worked with NGRX and, although is great (it's like magic when you set it all up), the boilerplate that you have to write in order to set a simple slice for the store is just annoying; literally, you have to write the state, selectors, reducers, effects, etc, etc. Of course, that if you use the full NGRX/platform; but still, it's quite some boilerplate.
I'll recommend you take a look to Akita which is a state management tool made by the folks at Datorama. I haven't use it (yet, I'm planning to use it on a project that is in the design stage) but their aim is to reduce the amount of boilerplate; plus, is great for people with OOP background (like myself) and they have a nice amount of funcionality built in for Angular (like pagination and form state).
When we are talking about state management I really think it's very important to realize what your app should do, how much business logic you should add on it.
For example, if you have a very complex flow and you always rely on some pieces of information from observables, for sure you need Effects. Effects are from ngrx and not in simple state management patterns (like Akita, Flux or any one of them).
If you just need to keep the state and everything it's pretty straight forward, simple subjects with observables are probably the best choice.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
I've worked with NGRX and, although is great (it's like magic when you set it all up), the boilerplate that you have to write in order to set a simple slice for the store is just annoying; literally, you have to write the state, selectors, reducers, effects, etc, etc. Of course, that if you use the full NGRX/platform; but still, it's quite some boilerplate.
I'll recommend you take a look to Akita which is a state management tool made by the folks at Datorama. I haven't use it (yet, I'm planning to use it on a project that is in the design stage) but their aim is to reduce the amount of boilerplate; plus, is great for people with OOP background (like myself) and they have a nice amount of funcionality built in for Angular (like pagination and form state).
Hope that helped!
Thanks a lot! I've read about Akita just yesterday. Will look more into it.
When we are talking about state management I really think it's very important to realize what your app should do, how much business logic you should add on it.
For example, if you have a very complex flow and you always rely on some pieces of information from observables, for sure you need Effects. Effects are from ngrx and not in simple state management patterns (like Akita, Flux or any one of them).
If you just need to keep the state and everything it's pretty straight forward, simple subjects with observables are probably the best choice.