Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Nest.js + Apollo GraphQL Federation + subscription #11987

Closed
1 task done
adamatti opened this issue Jul 6, 2023 · 1 comment
Closed
1 task done

Nest.js + Apollo GraphQL Federation + subscription #11987

adamatti opened this issue Jul 6, 2023 · 1 comment
Labels
needs triage This issue has not been looked into type: enhancement 🐺

Comments

@adamatti
Copy link

adamatti commented Jul 6, 2023

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

Not exactly a problem, but today graphql subscription is not supported using federation.

There is a explicit throw in the code about it here

    // class ApolloFederationDriver
    if (options.installSubscriptionHandlers || options.subscriptions) {
      // TL;DR <https://github.com/apollographql/apollo-server/issues/2776>
      throw new Error(
        'No support for subscriptions yet when using Apollo Federation',
      );
    }

Describe the solution you'd like

Graphql clients will be able to use subscription calling the federated service/gateway

Teachability, documentation, adoption, migration strategy

Not 100% sure how it would be implemented.
IMHO, no migration is needed

What is the motivation / use case for changing the behavior?

We have a microservices infrastructure and would like to have different services exposing subscriptions, so the client (ui / front) would be able to subscribe only knowing the federation gateway endpoint

@adamatti adamatti added needs triage This issue has not been looked into type: enhancement 🐺 labels Jul 6, 2023
@kamilmysliwiec
Copy link
Member

Duplicate nestjs/graphql#2879

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
needs triage This issue has not been looked into type: enhancement 🐺
Projects
None yet
Development

No branches or pull requests

2 participants