Proof of Concept Implementation of Graphql Live Queries in Node.js

Proof of Concept Implementation of Graphql Live Queries in Node.js

Real-Time with GraphQL for any GraphQL schema or transport. Proof of Concept Implementation of Graphql Live Queries in Node.js

Real-Time with GraphQL for any GraphQL schema or transport.

Read the blog post - Learn how operations are tracked

Packages in this Repository

Package Description Stats
@n1ru4l/in-memory-live-query-store Live query implementation. npm version npm downloads
@n1ru4l/graphql-live-query Utilities for live query implementations. npm version npm downloads
@n1ru4l/socket-io-graphql-server GraphQL over - Server Middleware npm version npm downloads
@n1ru4l/socket-io-graphql-client GraphQL over - Client npm version npm downloads
todo-example-app Todo App with state sync across clients. -


There are no mature live query implementation not tied to any specific database. This implementation should serve as an example how live queries can be added to any schema with (almost) and GraphQL transport.

GraphQL already has a solution for real-time: Subscriptions. Subscriptions are the right tool for responding to events. E.g. triggering a sound or showing a toast message once a new message has been received. Subscriptions are also often used for updating existing query results on the client. Depending on the complexity cache update code can eventually become pretty bloated. Often it is more straight-forward to simply refetch the query once a subscription event is received.

In contrast live queries should feel magically and update the UI with the latest data from the server without having to write any cache update wizardry code on the client.


A live query is a query operation that is annotated with a @live directive.

query users @live {
  users(first: 10) {

A live query is sent to the server (via a transport that supports delivering partial execution results) and registered. The client receives a immediate execution result and furthermore receives additional (partial) execution results once the live query operation was invalidated and therefore the client data became stale.

The client can inform the server that it is no longer interested in the query (unsubscribe the live query operation).

On the server we have a live query invalidation mechanism that is used for determining which queries have become stale, and thus need to be rescheduled for execution. In the future we might event be able to only re-execute partial subtrees of a query operation.

How does the server know the underlying data has changed?

The reference live query store implementation must be notified once a resource becomes stale.

A resource (in terms of the reference implementation) is described by a root query field schema coordinate (such as Query.viewer or Query.users), but also by a resource identifier (such as User:1). The latter is by default composed out of the resource typename and the non nullable id field of the given GraphQL type.

For the following type:

type User {
  id: ID!
  name: String!

A legitimate resource identifier would be User:1, User:2, User:dfsg12. Where the string after the first colon describes the id of the resource.

Practical example:

// somewhere inside a mutation resolver
await db.users.push(createNewUser());
// all live queries that select Query.users are invalidated and scheduled for re-execution.

How are the updates sent/applied to the client

The transport layer can be any transport that allows sending partial execution results to the client.

Most GraphQL clients (including GraphiQL) have support for Observable data structures which are perfect for describing both Subscription and Live Queries. Ideally a GraphQL Live Query implementation uses a Observable for pushing the latest query data to the client framework that consumes the data.

Inside this mono-repository there is GraphQL transport that uses WebSockets and HTTP polling.

Further optimizations could be achieved. E.g. the LiveQueryStore could only send patches to the client which should be applied to the initial query result or clients that have the same selection set could be merged so that the query must be only executed once when the underlying data changes.

A distributed backend with many clients could leverage a query store that relies on redis etc.

List of compatible transports/servers

List of known and tested compatible transports/servers. The order is alphabetical.

Package Transport Version Downloads
@n1ru4l/socket-io-graphql-server GraphQL over (WebSocket/HTTP Long Polling) npm version npm downloads
graphql-helix GraphQL over HTTP (IncrementalDelivery/SSE) npm version npm downloads
graphql-ws GraphQL over WebSocket npm version npm downloads

Download Details:

Author: n1ru4l

Source Code:

nodejs node javascript graphql

Bootstrap 5 Complete Course with Examples

Bootstrap 5 Tutorial - Bootstrap 5 Crash Course for Beginners

Nest.JS Tutorial for Beginners

Hello Vue 3: A First Look at Vue 3 and the Composition API

Building a simple Applications with Vue 3

Deno Crash Course: Explore Deno and Create a full REST API with Deno

How to Build a Real-time Chat App with Deno and WebSockets

Convert HTML to Markdown Online

HTML entity encoder decoder Online

GraphQL - How To Setup GraphQL Yoga Server with Node.js

Learn How To Setup GraphQL Yoga Server with Node.jS. Learn Set Up Graphql Server With Node and Graphql-Yoga.

Graphql Node JS ( Graphql Server & Client using Apollo ) # 12

Github : Graphql Client-Server (Complete Playlist)

Chat App by using Nodejs, Graphql, Mysql

chat-app .This is a chat app by using Nodejs, GraphQL, MySQL

Howw to Build and Deploy a Scalable GraphQL API with Nodejs

A walkthrough for creating and deploying a GraphQL API with Node.js. In this post, you'll see Howw to Build and Deploy a Scalable GraphQL API

GraphQL : How To Set Up GraphQL Server in Node.js with Apollo

Learn How To Set Up GraphQL Server in Node.js with Apollo & Express.