3 ms·
I haven't seen much mention of Apollo here. It offers a 'full stack' state management solution from server to client to offline cache. Each component can be ado
by reilly3000 7y ago
I haven't seen much mention of Apollo here. It offers a 'full stack' state management solution from server to client to offline cache. Each component can be adopted independently, but they work really nicely together. The tradeoff is that you're writing graphql, but it comes along with a lot of benefits, like consolidating requests etc. On the server-side, graphql can be a thin wrapper over rest apis. Defining good schemas can be a bit of a pain, but they maintain a level of consistency throughout the system as it grows.
- veeralpatel979 7y agoHi - author here. Thanks for mentioning Apollo. I've actually abandoned maintaining any data state in my global stores. I just use Apollo and provide a refetchQueries to my useMutation call to update my UI after mutations. https://www.apollographql.com/docs/react/api/react-hooks/ https://www.apollographql.com/docs/react/api/react-hooks/