Assuming I can end up using the Shopify Storefront (GraphQL) API, would you say that the approach mentioned here (Gateway API: https://medium.com/open-graphql/apollo-multiple-clients-with-react-b34b571210a5) is the best way to structure things to let Apollo pull data from multiple providers?

February 6, 2019 at 9:38pm

Jason Bahl@jasonbahl

Team

9:38pm

@paulisloud

I think the approach in that article works well. I've got one App that uses that approach and we haven't run into any major snags.

February 7, 2019 at 10:56am

Rafael Derolez@rafaelderolez

10:56am

I found someone else that just wraps another ApolloProvider around the first one: https://spectrum.chat/?t=4c8e2898-86b0-4706-9771-7940523634f0 and uses an as prop I can't find much about.

And then there's also react-apollo-multiple-clients: (https://github.com/titel-media/react-apollo-multiple-clients) which was made as a followup of that original Medium post.

Just to clarify: I don't know what the best way is, just sharing my findings.

Paul Grieselhuber@paulisloud

11:13am

Thanks for the feedback

@jasonbahl

11:15am

@rafaelderolez

that was my first thought, and it looks like the multiple client approach they've taken will indeed allow you to direct the right query to the right client. Thanks for sharing

11:16am

Will give both of these a shot

Rafael Derolez@rafaelderolez

11:28am

@paulisloud

If you get the first one to work, let me know! I didn't get far with the as prop.

I'm also wondering how this ties in with the Next.js's with-apollo example I'm using. It seems to extract the cache when using withApolloClient (https://github.com/zeit/next.js/blob/canary/examples/with-apollo/lib/with-apollo-client.js)

April 23, 2019 at 8:30am

Paul Grieselhuber@paulisloud

8:30am

At long last, here is the answer: https://www.loudnoises.us/next-js-two-apollo-clients-two-graphql-data-sources-the-easy-way/