3 ms·
TL;DR click bait. The author is replacing Redux with Apollo - a client side graphql library that HAS BUILT IN STATE MANAGEMENT, which he fails to differentiate
by nothrows 9y ago
TL;DR click bait. The author is replacing Redux with Apollo - a client side graphql library that HAS BUILT IN STATE MANAGEMENT, which he fails to differentiate or mention... Apollo is similar to the firebase event / subscription model.
https://dev-blog.apollodata.com/tutorial-graphql-subscriptions-client-side-40e185e4be76 https://dev-blog.apollodata.com/tutorial-graphql-subscriptio...
- wmdmark 9y agoDid you actually read the article? I explicitly mention that Apollo uses Redux as a cache under the hood (although that's not required).
- nothrows 9y agoI reread it several times trying to understand how simply using GraphQL allowed you to eliminate the need for all actions / stores for your entire client side stack. It wasn't until I looked into Apollo that I understood what you had actually implemented.
- wmdmark 9y agoApollo is mentioned 4 times in the article. That's beside the point though, even using GraphQL with plain old HTTP requests would have removed a lot of the need for Redux in our case.
- dntrkv 9y agoJust an fyi, Apollo no longer uses Redux under the hood.