You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is there an existing issue that is already proposing this?
I have searched the existing issues
Is your feature request related to a problem? Please describe it
I want to leverage the new subscriptions support in Apollo Federation but NestJS's docs cause me to think that it isn't supported yet in @nestjs/graphql.
I've been trying to contribute for the community the way to implement Apollo Subscriptions into Nestjs. I will tell you what is my conclusion after all the research and tries.
Conclusion: You cannot implement it in the free version. Link. However, it's viable with the enterprise version.
In nestjs we use Apollo Gateway and Apollo Subgraph. However, Apollo gateway are not design to support realtime requests: Link. The good news are that Apollo create Apollo Router that improve a lot of things including support for Subscriptions.
You have many differences between using Apollo Gateway and Apollo Router. The main one is that Apollo router is not a npm package instead of it, it is a binary package that you need to download and use it.
I could implement apollo router with all the configurations and I could modify the ApolloFederationDriver to support subscriptions. The problem is when you would like to enable the subscriptions in the router. Because it is an enterprise feature.
@kamilmysliwiec Do you think it is a good idea to implement it anyway?
Is there an existing issue that is already proposing this?
Is your feature request related to a problem? Please describe it
I want to leverage the new subscriptions support in Apollo Federation but NestJS's docs cause me to think that it isn't supported yet in @nestjs/graphql.
https://www.apollographql.com/blog/announcement/backend/federated-subscriptions-in-graphos-real-time-data-at-scale/#subscriptions-meet-apollo-federation
From https://docs.nestjs.com/graphql/federation:
Describe the solution you'd like
Updated docs, support, and example of using subscriptions with Apollo Federation using @nestjs/graphql.
Teachability, documentation, adoption, migration strategy
No response
What is the motivation / use case for changing the behavior?
Build microservices that can be used by a client as one GraphQL API even with subscriptions across those microservices.
The text was updated successfully, but these errors were encountered: