@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.

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.

Thanks for the feedback @jasonbahl

@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

Will give both of these a shot

@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)

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