Skip to main content

GraphQL Subscriptions In Angular Using Apollo Angular Library

In this article, we are going to understand GraphQL Subscriptions in an angular application using the Apollo Angular Library.

Graphql Subscription:

GraphQL subscriptions are a way to push data from the server to the clients that listen to real-time messages or payload or data from the server. Subscriptions are similar to queries in that they specify a set of fields to be delivered to the client, but instead of immediately returning a single response, a result is sent every time a particular event happens on the server.

So for this demo, I have created a GraphQL endpoint in .Net5. So I'm going to use that as my server.



So above 2 images like 'Publisher' and 'Subscriber' are tested using the browser. Now we will implement those publisher and subscriber functionalities into the angular application.

Create An Angular Application:

Let's begin our demo by creating an angular sample application.
Command To Install Angular CLI:(If not installed on your system previously)
npm install -g @angular/cli
Angular CLI Command To Create Angular App:
ng new your_project_name
Command To Run App:
ng serve

Install Required Apollo Angular Packages:

Apollo Angular provides us an easy way to install and configure it into our application with a simple 'ng' command below.
Command To Install And Setup Apollo Angular :
ng add apollo-angular
The above command installs 3 different libraries like 'apollo-angular', '@apollo/client', 'graphql'.
The 'graphql.module.ts' a new file will be created with all startup configurations regarding GraphQL.

Subscriptions need a persistent connection, so we are going to use WebSockets. To work with WebSockets we need the following libraries.
npm install --save subscriptions-transport-ws
npm i --save-dev @types/ws 

Configure HTTP And WebSocket Url In GraphQL Module:

GraphQL 'Queries', 'Mutations' are carried over the HTTP URL.

GraphqQL 'Subscriptions' need persistent connection, so subscriptions carried over WebSockets.

Now in the GraphQL module, we have to manage the URL by switching them based on GraphQL operation. So let's update the 'createApollo' method inside of the 'graphql.module.ts'.
import {NgModule} from '@angular/core';
import {APOLLO_OPTIONS} from 'apollo-angular';
import {ApolloClientOptions, InMemoryCache, split} from '@apollo/client/core';
import {HttpLink} from 'apollo-angular/http';
import {WebSocketLink} from '@apollo/client/link/ws';
import {getMainDefinition} from '@apollo/client/utilities';

export function createApollo(httpLink: HttpLink): ApolloClientOptions<any> {

  const http = httpLink.create({

  const ws = new WebSocketLink({

  const link = split(
    ({query}) => {
      const data = getMainDefinition(query);
      return (
        data.kind === 'OperationDefinition' && data.operation === 'subscription'

  return {
    link: link,
    cache: new InMemoryCache(),

  providers: [
      provide: APOLLO_OPTIONS,
      useFactory: createApollo,
      deps: [HttpLink],
export class GraphQLModule {}
  • (Line: 10-12) Creating the HTTP instance with its URL registering.
  • (Line: 14-19) Creating the WebSocket instance with its URL registering.
  • (Line: 21-30) The 'split' function loads from '@apollo/client/core'. This 'split' function works conditional loader where based on the operations('query', 'mutation', 'subscriptions') triggered from our angular app appropriate URL instance will be loaded.

Basic Components Creation:

In our sample, we will create 2 components. One component will have a user form, here we will invoke GraphQL mutation to send the data to the server. Another component is the subscription component where we implement our GraphQL subscription logic to continuously receive data from the server.

So let's create components like 'create.product.ts' and 'subscribe.product.ts'.
Now configure the routing for our components.
Now import our newly added components into the 'app.module.ts'.

Mutation Operation:

Now we have to implement a mutation operation that sends data to the server. So we are going to create a small form to post the data to the server in 'subscribe.product.ts'. So 'subscribe.product.ts' component will our publisher.

<h3>Products Form</h3>
  <div class="mb-3">
    <label for="productName" class="form-label">Name</label>
    <input class="form-control" name="productName" [(ngModel)]="" type="text"  />
  <div class="mb-3">
    <label for="productPrice" class="form-label">Price</label>
    <input class="form-control" name="productPrice" type="text" [(ngModel)]="productsForm.cost" />
  <button type="button" (click)="send()" class="btn btn-warning">Send</button>
import { Component } from '@angular/core';
import { Apollo, gql } from 'apollo-angular';

const post_Product = gql`
  mutation($myProduct: ProductInput) {
    addProduct(model: $myProduct)

  templateUrl: 'create.product.html',
export class CreateProduct {
   productsForm = {
    name: '',
    cost: '',

  constructor(private apollo: Apollo) {}

  send() {
        mutation: post_Product,
        variables: {
          myProduct: {
              cost:  Number(this.productsForm.cost)
      .subscribe(({ data }) => {
  • (Line: 4-8) Framed GraphQL mutation.
  • (Line: 14-17) The 'productForm' variable declared to enable data binding with the form.
  • (Line: 19) Injecting 'Apollo' instance.
  • (Line: 21-35) Invoking the GraphQL endpoint. Our form data is assigned to the GraphQL variable.

Subscription Operation:

GraphQL subscription is similar to the query, but the query is like single time receiving response whereas the subscription is like continuous listening for responses from the server.

So in the Apollo Angular library implementing subscription is not straightforward like in query or mutations. So to enable subscription initially we need to create the instance of the query, so from the query instance, we will enable our subscription. 

For example, need to fetch record automatically from the server without calling it manually, in that case initially data will be fetched by using the GraphQL query, next we will derive subscription so that all other latest record automatically received from the server continuously. In some cases, we don't have initial data to load and we need to enable subscriptions, then we can create a fake query instance(never read the result here) and then derive the subscription.

Now in 'subscription.product.ts' implement the GraphQL subscription logic. So 'subscription.product.ts' component will be the subscriber.

<h3>Subscription To Fetch Latest Product</h3>
<ul *ngIf="productData">
    <li><span>Name</span>  {{}}</li>
    <li><span>Cost</span>  {{productData.cost}}</li>
    <li><span>Date</span>  {{productData.createdDate}}</li>
import { Component, OnInit } from "@angular/core";
import { Apollo, gql, QueryRef } from "apollo-angular";

const dummy = gql`query{fakequery}`;

const sub = gql`subscription{

export class SubscribeProduct implements OnInit{
    queryRef: QueryRef<any>;

    constructor(private apollo:Apollo){
        this.queryRef = this.apollo.watchQuery({
    ngOnInit(): void {


            document: sub,
            updateQuery:(prev, {subscriptionData})  =>{
                this.productData =;
  • (Line: 4) Added some fake GraphQL query commands. (If you want to load data initially with GraphQL query command then give the valid command, in my case I want only subscription and don't care about the initial data)
  • (Line: 6-12) Added the subscription command.
  • (Line: 20) Declared 'QueryRef<any>' variable.
  • (Line: 23-25) Here I'm framing the GraphQL query operation and assigning its reference to 'queryRef' variable. Here I'm not making calls to API.
  • (Line: 34-40) Here using 'queryRef' variable memory we are enabling our subscription by calling the 'subscribeToMore' method. To the 'document' property we need to pass the subscription command. To the 'updateQuery' property we have to register the callback method, which gets executed on every response send by the server. So the subscription is a persistent connection carried over WebSocket.
Now to test run both server and angular application. Now in the browser tab open the angular page "http://localhost:4200/subscribe-product" which is our subscriber. (you can open this page in the n-number of a browser tab, all will listen for server response)
Now in the open angular home page which is the publisher. Enter some data and submit.
Now check all subscriber page browser tabs.
So that's all about implementing GraphQL Subscription in angular application.

Video Session:

Support Me!
Buy Me A Coffee PayPal Me

Wrapping Up:

Hopefully, I think this article delivered some useful information on implementing GraphQL Subscription in the angular application using Apollo Angular library. I love to have your feedback, suggestions, and better techniques in the comment section below.

Follow Me:


  1. When using SubscribeToMore in an angular component, this code fires multiple times. How can it be made to fire only once, or how can that code be unsubscribed?


Post a Comment

Popular posts from this blog

.NET6 Web API CRUD Operation With Entity Framework Core

In this article, we are going to do a small demo on AspNetCore 6 Web API CRUD operations. What Is Web API: Web API is a framework for building HTTP services that can be accessed from any client like browser, mobile devices, desktop apps. In simple terminology API(Application Programming Interface) means an interface module that contains a programming function that can be requested via HTTP calls to save or fetch the data for their respective clients. Some of the key characteristics of API: Supports HTTP verbs like 'GET', 'POST', 'PUT', 'DELETE', etc. Supports default responses like 'XML' and 'JSON'. Also can define custom responses. Supports self-hosting or individual hosting, so that all different kinds of apps can consume it. Authentication and Authorization are easy to implement. The ideal platform to build REST full services. Create A .NET6 Web API Application: Let's create a .Net6 Web API sample application to accomplish our

A Small Guide On NestJS Queues

NestJS Application Queues helps to deal with application scaling and performance challenges. When To Use Queues?: API request that mostly involves in time taking operations like CPU bound operation, doing them synchronously which will result in thread blocking. So to avoid these issues, it is an appropriate way to make the CPU-bound operation separate background job.  In nestjs one of the best solutions for these kinds of tasks is to implement the Queues. For queueing mechanism in the nestjs application most recommended library is '@nestjs/bull'(Bull is nodejs queue library). The 'Bull' depends on Redis cache for data storage like a job. So in this queueing technique, we will create services like 'Producer' and 'Consumer'. The 'Producer' is used to push our jobs into the Redis stores. The consumer will read those jobs(eg: CPU Bound Operations) and process them. So by using this queues technique user requests processed very fastly because actually

Part-1 Angular JWT Authentication Using HTTP Only Cookie[Angular V13]

In this article, we are going to implement a sample angular application authentication using HTTP only cookie that contains a JWT token. HTTP Only JWT Cookie: In a SPA(Single Page Application) Authentication JWT token either can be stored in browser 'LocalStorage' or in 'Cookie'. Storing JWT token inside of the cookie then the cookie should be HTTP Only. The HTTP-Only cookie nature is that it will be only accessible by the server application. Client apps like javascript-based apps can't access the HTTP-Only cookie. So if we use authentication with HTTP only JWT cookie then we no need to implement custom logic like adding authorization header or storing token data, etc at our client application. Because once the user authenticated cookie will be automatically sent to the server by the browser on every API call. Authentication API: To implement JWT cookie authentication we need to set up an API. For that, I had created a mock authentication API(Using the NestJS Se

Usage Of CancellationToken In Asp.Net Core Applications

When To Use CancellationToken?: In a web application request abortion or orphan, requests are quite common. On users disconnected by network interruption or navigating between multiple pages before proper response or closing of the browser, tabs make the request aborted or orphan. An orphan request can't deliver a response to the client, but it will execute all steps(like database calls, HTTP calls, etc) at the server. Complete execution of an orphan request at the server might not be a problem generally if at all requests need to work on time taking a job at the server in those cases might be nice to terminate the execution immediately. So CancellationToken can be used to terminate a request execution at the server immediately once the request is aborted or orphan. Here we are going to see some sample code snippets about implementing a CancellationToken for Entity FrameworkCore, Dapper ORM, and HttpClient calls in Asp.NetCore MVC application. Note: The sample codes I will show in

Unit Testing Asp.NetCore Web API Using xUnit[.NET6]

In this article, we are going to write test cases to an Asp.NetCore Web API(.NET6) application using the xUnit. xUnit For .NET: The xUnit for .Net is a free, open-source, community-focused unit testing tool for .NET applications. By default .Net also provides a xUnit project template to implement test cases. Unit test cases build upon the 'AAA' formula that means 'Arrange', 'Act' and 'Assert' Arrange - Declaring variables, objects, instantiating mocks, etc. Act - Calling or invoking the method that needs to be tested. Assert - The assert ensures that code behaves as expected means yielding expected output. Create An API And Unit Test Projects: Let's create a .Net6 Web API and xUnit sample applications to accomplish our demo. We can use either Visual Studio 2022 or Visual Studio Code(using .NET CLI commands) to create any.Net6 application. For this demo, I'm using the 'Visual Studio Code'(using the .NET CLI command) editor. Create a fo

Blazor WebAssembly Custom Authentication From Scratch

In this article, we are going to explore and implement custom authentication from the scratch. In this sample, we will use JWT authentication for user authentication. Main Building Blocks Of Blazor WebAssembly Authentication: The core concepts of blazor webassembly authentication are: AuthenticationStateProvider Service AuthorizeView Component Task<AuthenticationState> Cascading Property CascadingAuthenticationState Component AuthorizeRouteView Component AuthenticationStateProvider Service - this provider holds the authentication information about the login user. The 'GetAuthenticationStateAsync()' method in the Authentication state provider returns user AuthenticationState. The 'NotifyAuthenticationStateChaged()' to notify the latest user information within the components which using this AuthenticationStateProvider. AuthorizeView Component - displays different content depending on the user authorization state. This component uses the AuthenticationStateProvider

Angular 14 Reactive Forms Example

In this article, we will explore the Angular(14) reactive forms with an example. Reactive Forms: Angular reactive forms support model-driven techniques to handle the form's input values. The reactive forms state is immutable, any form filed change creates a new state for the form. Reactive forms are built around observable streams, where form inputs and values are provided as streams of input values, which can be accessed synchronously. Some key notations that involve in reactive forms are like: FormControl - each input element in the form is 'FormControl'. The 'FormControl' tracks the value and validation status of form fields. FormGroup - Track the value and validate the state of the group of 'FormControl'. FormBuilder - Angular service which can be used to create the 'FormGroup' or FormControl instance quickly. Form Array - That can hold infinite form control, this helps to create dynamic forms. Create An Angular(14) Application: Let'

How Response Caching Works In Asp.Net Core

What Is Response Caching?: Response Caching means storing of response output and using stored response until it's under it's the expiration time. Response Caching approach cuts down some requests to the server and also reduces some workload on the server. Response Caching Headers: Response Caching carried out by the few Http based headers information between client and server. Main Response Caching Headers are like below Cache-Control Pragma Vary Cache-Control Header: Cache-Control header is the main header type for the response caching. Cache-Control will be decorated with the following directives. public - this directive indicates any cache may store the response. private - this directive allows to store response with respect to a single user and can't be stored with shared cache stores. max-age - this directive represents a time to hold a response in the cache. no-cache - this directive represents no storing of response and always fetch the fr

Different HttpClient Techniques To Consume API Calls In Minimal API[.NET6]

In this article, we are going to implement different HttpClient techniques to consume API calls in minimal API. The different HttpClient techniques that we are going to explore are like: Register HttpClient Object Explicitly In DI(Dependency Injection Service) Named Client Type Client HttpRequestMessage Object Create A .NET6 Minimal API Project: Let's create a .Net6 Minimal API sample project to accomplish our demo. We can use either Visual Studio 2022 or Visual Studio Code(using .NET CLI commands) to create any.Net6 application. For this demo, I'm using the 'Visual Studio Code'(using the .NET CLI command) editor. CLI command For Minimal API Project dotnet new webapi -minimal -o Your_Project_Name Create A Third Party API Response Model: Here I'm going to use a free third-party rest API that is "". So to receive the response let's create a response model like 'Post.cs'. Program.cs:(Add Post.cs c

.Net5 Web API Managing Files Using Azure Blob Storage

In this article, we are going to understand the different file operations like uploading, reading, downloading, and deleting in .Net5 Web API application using Azure Blob Storage. Azure Blob Storage: Azure blob storage is Microsoft cloud storage. Blob storage can store a massive amount of file data as unstructured data. The unstructured data means not belong to any specific type, which means text or binary data. So something like images or pdf or videos to store in the cloud, then the most recommended is to use the blob store. The key component to creating azure blob storage resource: Storage Account:- A Storage account gives a unique namespace in Azure for all the data we will save. Every object that we store in Azure Storage has an address. The address is nothing but the unique name of our Storage Account name. The combination of the account name and the Azure Storage blob endpoint forms the base address for each object in our Storage account. For example, if our Storage Account is n