graphql-subscriptions-continued

GraphQL subscriptions continued is a copy of the original graphql-subscriptions which seems to be (near) abandoned.

Since I was tired of waiting for the v3 release to be made, I've made it myself now. It should work identical to the original version, but with the version as of the release-3.0 branch. This hopefully means it'll be compatible with graphql-code-generator again.

There's alternatives to this library, but people with existing code probably want to migrate with as little fuzz as possible, so this retains the exact same interface.

graphql-subscriptions

GraphQL subscriptions is a simple npm package that lets you wire up GraphQL with a pubsub system (like Redis) to implement subscriptions in GraphQL.

You can use it with any GraphQL client and server (not only Apollo).

$3

npm install graphql-subscriptions-continued graphql or yarn add graphql-subscriptions-continued graphql

> This package should be used with a network transport, for example graphql-ws.

$3

If you are developing a project that uses this module with TypeScript:

* ensure that your tsconfig.json lib definition includes "es2018.asynciterable"
* npm install @types/graphql or yarn add @types/graphql

$3

To begin with GraphQL subscriptions, start by defining a GraphQL Subscription type in your schema:

``graphql
type Subscription {
somethingChanged: Result
}

type Result {
id: String
}
`

Next, add the Subscription type to your schema definition:

`graphql
schema {
query: Query
mutation: Mutation
subscription: Subscription
}
`

Now, let's create a simple PubSub instance - it is a simple pubsub implementation, based on EventEmitter. Alternative EventEmitter implementations can be passed by an options object
to the PubSub constructor.

`js
import { PubSub } from 'graphql-subscriptions-continued';

export const pubsub = new PubSub();
`

If you're using TypeScript you can use the optional generic parameter for added type-safety:

`ts
import { PubSub } from "apollo-server-express";

const pubsub = new PubSub<{
EVENT_ONE: { data: number; };
EVENT_TWO: { data: string; };
}>();

pubsub.publish("EVENT_ONE", { data: 42 });
pubsub.publish("EVENTONE", { data: 42 }); // ! ERROR
pubsub.publish("EVENT_ONE", { data: "42" }); // ! ERROR
pubsub.publish("EVENT_TWO", { data: "hello" });

pubsub.subscribe("EVENT_ONE", () => {});
pubsub.subscribe("EVENTONE", () => {}); // ! ERROR
pubsub.subscribe("EVENT_TWO", () => {});
`

Next implement your Subscriptions type resolver using the pubsub.asyncIterator to map the event you need:

`js
const SOMETHING_CHANGED_TOPIC = 'something_changed';

export const resolvers = {
Subscription: {
somethingChanged: {
subscribe: () => pubsub.asyncIterator(SOMETHING_CHANGED_TOPIC),
},
},
}
`

> Subscriptions resolvers are not a function, but an object with subscribe method, that returns AsyncIterable.

The GraphQL engine now knows that somethingChanged is a subscription, and every time we use pubsub.publish it will publish content using our chosen transport layer:

`js
pubsub.publish(SOMETHING_CHANGED_TOPIC, { somethingChanged: { id: "123" }});
`

> Note that the default PubSub implementation is intended for demo purposes. It only works if you have a single instance of your server and doesn't scale beyond a couple of connections.
> For production usage you'll want to use one of the PubSub implementations backed by an external store. (e.g. Redis)

$3

When publishing data to subscribers, we need to make sure that each subscriber gets only the data it needs.

To do so, we can use withFilter helper from this package, which wraps AsyncIterator with a filter function, and lets you control each publication for each user.

withFilter API:
- asyncIteratorFn: (rootValue, args, context, info) => AsyncIterator : A function that returns AsyncIterator you got from your pubsub.asyncIterator.
- filterFn: (payload, variables, context, info) => boolean | Promise - A filter function, executed with the payload (the published value), variables, context and operation info, must return boolean or Promise indicating if the payload should pass to the subscriber.

For example, if somethingChanged would also accept a variable with the ID that is relevant, we can use the following code to filter according to it:

`js
import { withFilter } from 'graphql-subscriptions-continued';

const SOMETHING_CHANGED_TOPIC = 'something_changed';

export const resolvers = {
Subscription: {
somethingChanged: {
subscribe: withFilter(() => pubsub.asyncIterator(SOMETHING_CHANGED_TOPIC), (payload, variables) => {
return payload.somethingChanged.id === variables.relevantId;
}),
},
},
}
`

> Note that when using withFilter, you don't need to wrap your return value with a function.

$3

You can map multiple channels into the same subscription, for example when there are multiple events that trigger the same subscription in the GraphQL engine.

`js
const SOMETHING_UPDATED = 'something_updated';
const SOMETHING_CREATED = 'something_created';
const SOMETHING_REMOVED = 'something_removed';

export const resolvers = {
Subscription: {
somethingChanged: {
subscribe: () => pubsub.asyncIterator([ SOMETHING_UPDATED, SOMETHING_CREATED, SOMETHING_REMOVED ]),
},
},
}
``

$3

You can also manipulate the published payload, by adding resolve methods to your subscription:

`js
const SOMETHING_UPDATED = 'something_updated';

export const resolvers = {
Subscription: {
somethingChanged: {
resolve: (payload, args, context, info) => {
// Manipulate and return the new value
return payload.somethingChanged;
},
subscribe: () => pubsub.asyncIterator(SOMETHING_UPDATED),
},
},
}
``

Note that resolve methods execute after subscribe, so if the code in subscribe depends on a manipulated payload field, you will need to factor out the manipulation and call it from both subscribe and resolve.

$3

Your database might have callback-based listeners for changes, for example something like this:

`JS
const listenToNewMessages = (callback) => {
return db.table('messages').listen(newMessage => callback(newMessage));
}

// Kick off the listener
listenToNewMessages(message => {
console.log(message);
})
`

The callback function would be called every time a new message is saved in the database. Unfortunately, that doesn't play very well with async iterators out of the box because callbacks are push-based, where async iterators are pull-based.

We recommend using the callback-to-async-iterator module to convert your callback-based listener into an async iterator:

`js
import asyncify from 'callback-to-async-iterator';

export const resolvers = {
Subscription: {
somethingChanged: {
subscribe: () => asyncify(listenToNewMessages),
},
},
}
``

$3

The value you should return from your subscribe resolver must be an AsyncIterator.

You can use this value and wrap it with another AsyncIterator to implement custom logic over your subscriptions.

For example, the following implementation manipulates the payload by adding some static fields:

`typescript
export const withStaticFields = (asyncIterator: AsyncIterator, staticFields: Object): Function => {
return (rootValue: any, args: any, context: any, info: any): AsyncIterator => {

return {
next() {
return asyncIterator.next().then(({ value, done }) => {
return {
value: {
...value,
...staticFields,
},
done,
};
});
},
return() {
return Promise.resolve({ value: undefined, done: true });
},
throw(error) {
return Promise.reject(error);
},
[Symbol.asyncIterator]() {
return this;
},
};
};
};
`

> You can also take a look at withFilter for inspiration.

$3

It can be easily replaced with some other implementations of PubSubEngine abstract class. Here are a few of them:
- Use Redis with https://github.com/davidyaha/graphql-redis-subscriptions
- Use Google PubSub with https://github.com/axelspringer/graphql-google-pubsub
- Use MQTT enabled broker with https://github.com/aerogear/graphql-mqtt-subscriptions
- Use RabbitMQ with https://github.com/cdmbase/graphql-rabbitmq-subscriptions
- Use AMQP (RabbitMQ) with https://github.com/Surnet/graphql-amqp-subscriptions
- Use Kafka with https://github.com/ancashoria/graphql-kafka-subscriptions
- Use Kafka (using Kafkajs) with https://github.com/tomasAlabes/graphql-kafkajs-subscriptions
- Use Postgres with https://github.com/GraphQLCollege/graphql-postgres-subscriptions
- Use NATS with https://github.com/moonwalker/graphql-nats-subscriptions
- Use Mongoose (MongoDB) with https://github.com/Nickolasmv/graphql-mongoose-subscriptions
- Use multiple backends with https://github.com/jcoreio/graphql-multiplex-subscriptions
- Use Ably for multi-protocol support with https://github.com/ably-labs/graphql-ably-pubsub
- Use Google Firestore with https://github.com/m19c/graphql-firestore-subscriptions
- Use Amazon's Simple Notification Service (SNS) and Simple Queue Service (SQS) with https://github.com/sagahead-io/graphql-snssqs-subscriptions
- Add your implementation...

You can also implement a PubSub of your own, by using the exported abstract class PubSubEngine from this package. By using extends PubSubEngine you use the default asyncIterator method implementation; by using implements PubSubEngine you must implement your own AsyncIterator`.