For the last year I've been using react context as my global state solution with some useReducer magic here and there, and I'm very happy with the results. I miss how easy was to use middlewares, but there's always a workaround.
I just started using Apollo lately, and if you use GraphQL, it also works pretty well!
Nope, good thing about using Context, you can create more than one. Also, only the components "subscribed" to a context will rerender if the context changes. It's basically the same as REDUX.
For the last year I've been using react context as my global state solution with some useReducer magic here and there, and I'm very happy with the results. I miss how easy was to use middlewares, but there's always a workaround.
I just started using Apollo lately, and if you use GraphQL, it also works pretty well!
you don't use Redux but just use a context? does that mean when data updates the whole App's components render() are called?
Nope, good thing about using Context, you can create more than one. Also, only the components "subscribed" to a context will rerender if the context changes. It's basically the same as REDUX.
You have a great example of how to do it here: kentcdodds.com/blog/how-to-use-rea...