How to handle multi about next-with-apollo HOT 4 CLOSED

Yes I looked into schema stitching, but I will look for another solution. Thank you for your help.

from next-with-apollo.

I don't think that it's recommended to have multiple Apollo Clients, what's your use case and why do you need multiple clients ?, - There may be a solution but it will not look good.

from next-with-apollo.

Yes we are connecting with Shopify's GraphQL API. Shopify has a package to mount the GraphQL client side (localhost:3000/graphql). Currently, we are calling the Shopify API on our graphQL server so only 1 client is used, but we would like to allow users to access the Shopify API without the backend if they choose to do so.

from next-with-apollo.

Okay, but do you understand that Apollo Devtools may not work, you will have multiple caches, and also that SSR will be much harder ? specially because you'll need to specify the Apollo client to use per query (And I'm not sure if SSR will work for that).

A better solution can be to merge your schema with Shopify's one using schema stitching, one of the principles of GraphQL is to have one single source of truth, so it does make more sense.

from next-with-apollo.