Multiple instances for ApolloClient?

[silver robin]

In the docs there is a suggestion to add prisma to the global namespace (https://remix.run/docs/en/1.14.1/tutorials/jokes#md-connect-to-the-database). I would like to know if this is recommended for Apollo Client as well. My Apollo Client points to my backend (separate application) GraphQL endpoint, this means that I don't have a direct connection to the database.

[mellow shuttle]

My understanding is if you have something that needs to open and close connections when you’re using it then you want that global namespace for development. This is so you don’t have to call client.disconnect and client.connect every time you make a change in development. If your client tried to keep open a connection for data access you should follow that global pattern

To me it seems like the Apollo client is half a front end framework for like react fetching. If that’s the case, you don’t need to worry about the global. Since it seems your front end is responsible for creating an instance on each user.

[silver robin]

Thank you for the response!

Since it seems your front end is responsible for creating an instance on each user.

I'm not using Apollo Client in the client. My data fetching is still in the loader function.

[mellow shuttle]

If you’re doing it on the server the global may make sense. You can experiment and try without it first. The issue the global is trying to resolve is many many clients being made and just floating. You’ll notice your application can start slowing down as you open more and more clients for each time you make a code change. If you see more resources getting used or if you see warnings from the library itself, then definitely go with the global implementation

If you were to kill the process though your next dev start will be fresh and shouldn’t have any issues. So the worst case is you notice performance issues only in development without the global