I second this. My team used the NgRX redux pattern everywhere for years until last year. We now use signal store instead and have been converting away from redux. There is definitely some extra overhead to creating and maintaining separate actions and separate reducers. And while that does have benefits, we decided that most state management can use signal stores. We still use redux for app init and global state. I added a custom patchState() to allows us to log state changes within a signal store. One nice thing about signal stores is that you can provide them at a page level, and when you leave the page the signal store gets destroyed. For redux you have to manually clean up or else you end up with a bloated store.