Oh yeah one more question. If I had two ApolloClients and I wanted them to share a cache, would it be okay to write a NormalizedCacheFactory that always returns the same instance? Or would that have undesirable consequences?

That wouldn't work cause the locking is in

ApolloStore

We have a few client instances at the moment, but I'm not entirely sure why. We were using our own client, based on OkHttp, which was originally written several years ago. Now I'm going through the process of replacing them with ApolloClients, and I'm trying to think if it'd be easier to combine them into one client or to share a cache among several clients.

We use different client combinations for memory, disk and memory, and no cache in our app with no issues. They share same DI instance . We don’t mix calling them together on same page at once in different strategies too often, but seemingly works fine.

Nice, I like that idea