pullstate VS spring-boot-starter

PullState - https://lostpebble.github.io/pullstate/

Pullstate. It's a lot like svelte's store.

And automatically, any components using uiStateStore.useState and watching the isSidebarOpen property will get updated, exactly the same as the normal useState hook - just shared.

It's so dead simple and has made complex app-building so much easier for me.

The one caveat is that if I have a component with many handlers, e.g. onClick, onMouseMove, onContextMenu, onMouseLeave, etc (and in some cases I do), components can get bloated. I haven't found a fix to that yet. But that's more an inherent issue with react than anything to do with state management.

[1] https://github.com/lostpebble/pullstate

Sounds like you're on the right track. React is very hire-able. Try out multiple store systems. The big one is react + redux. Then after you have some experience with that, try a simpler one like pullstate.

You could try out pullstate - its basically just global objects which you can mutate and which automatically update your state over your entire app, for whichever parts you have "pulled" the state into.

You may find that after getting a good amount of foundational knowledge or experience, books are only good for author perspective. In the wild, maybe you'll benefit more from a boilerplate / starter repo like this or this. Those are called starters / boilerplate repos. That's a good way to get started if the getting started docs of your chosen tech is intimidating or confusing. Here's the one for spring boot.