At the time of release of Apollo Server 3, the protocol used in the graphql-ws library is not yet supported by GraphQL Playground or Apollo Explorer, which is why we do not yet document it as our main recommendation for a subscriptions library. The two libraries implement different protocols for GraphQL subscriptions over websockets, so you will need to adjust your client to support graphql-ws.
A newer alternative to subscriptions-transport-ws called graphql-ws is currently more actively maintained, and its README explains how to use it with Apollo Server. However, as of 2021, this library is not actively maintained.
This page explains how to connect the subscriptions-transport-ws library to your Apollo Server. If you create a new open-source library, click Edit on GitHub to let us know about it! The graphql-ws transport library If none of these libraries fits your use case, you can also create your own PubSubEngine subclass. The following are community-created PubSub libraries for popular event-publishing systems: Instead, you should use a subclass of the PubSubEngine abstract class that you can back with an external datastore such as Redis or Kafka. This means that events published by one instance of your GraphQL server are not received by subscriptions that are handled by other instances. Production PubSub librariesĪs mentioned above, the PubSub class is not recommended for production environments, because its event-publishing system is in-memory. In case of an authentication error, the Promise will be rejected, which prevents the client's connection. The user object found will be available as context.currentUser in your GraphQL resolvers. The example above looks up a user based on the auth token that is sent with the first initialization message on the transport, then returns the user object as a Promise.
0 kommentar(er)
