server VS use-context-selector

PS: Check Tolgee.io and give us github stars

To learn more visit our website [tolgee.io](https://tolgee.io)

I am not sure it it's documented somewhere, but you can also select custom fields it's automatically mapped to the interface. So it's pretty useful for complex queries with lot of joined columns. I use it a lot in Tolgee code. Check this line in one of our JPA repositories:

It's from third party maintainer, thats true, but it's downloaded directly from tolgee.io's resources. Can you please share, which ad block do you use? Thanks!

OK! And what is Tolgee?

PS: Check Tolgee.io and give us github stars

Hi there! Seems cool! Have you considered localization of the platform? We develop open-source tool for web app localization - Tolgee. Let's chat if we can help you! :)

For deploying the application to the cloud, I recommend running it in multiple containers or use database managed by your cloud provider. In Tolgee we use Kubernetes for deploying our Application container and DigitalOcean's managed PostgreSQL DB, so we don't have to worry about the database cluster.

Tolgee

Use jotai, or as someone else mentioned, zustand. React Context out of the box requires a very deliberate mental model due to a lack of tooling around selecting slices of state. This is why packages like react-context-selector exist: https://github.com/dai-shi/use-context-selector

Unless I've missed it, context doesn't have selector IIRC. You'd have to use a third party solution useContextSelector

How does this differ from https://github.com/dai-shi/use-context-selector?

you can always split out context state or use a library to help with rerender issues like https://github.com/dai-shi/use-context-selector, or just switch to jotai or something else if you want something more ergonomic or better design patterns.

If you don't want to swap out useContext, you could always use useContextSelector, which helps you limit what props in the context should rerender the component.

I wouldn't call this easy

It wouldn't be clear to anyone learning Context API either. At least, not using official docs. Because Context API is not supposed for state management, and if you for some unknown reasons try to roll your own state management on top of it, you have to use tricky libraries to work around the issues resulting from such abuse.

Any time anything in the context changes, any component that is consuming it will re-render. If you use it for frequently changed values, this library is needed to reduce unnecessary re-renders.

Use of this implementation of useContextSelector

Another technology I use regularly is Redux. But this time I wanted to manage the global state in a simpler and clearer way just using React hooks. I decided to go with a simple useReducer combined with theuseContextSelector hook which will avoid the whole application’s re-render caused by the native useContext hook.