Skip to main content

NestJS API Integration With GraphQL Using Schema First Approach

What Is GraphQL?:

GraphQL is a query language for your API and a server-side runtime for executing queries by using a schema type system you defined for your data. Graphql is not tied to any specific programming language(like NestJS, Java, .NET, etc) or database or storage engine.

How GraphQL Different From Rest API:

  • GraphQL exposes a single endpoint.
  • HTTP-POST is the only Http verb recommended by GraphQL.
  • Client applications(consumers of GraphQL API) can give instructions to GraphQL API about the response data.

Schema vs Code First Approach:

Schema First Approach - GraphQL SDL (Schema definition language) is a new syntax language, which is independent of any programming language and also integrates with any programming language. But while integrating with any programming language GraphQL Schema needs to be mapped with objects or classes or interface of the specific programming language to build communication between GraphQL Schema and programming language. In NestJS this communication channel will be built automatically by generating files in the form Typescript Classes or Interfaces based on the GraphQL schema define by you.

Code First Approach - In this approach TypeScript Classes and its fields use decorators on them which will generate corresponding GraphQL Schema automatically. Here we don't specify GraphQL SDL explicitly which helps developers to have less concentration on GraphQL Schema syntax.

Create NestJS Application:

Here we going to create a sample NestJS application with GraphQL integration using Schema first Approach.
NestJS Installation Command:
npm i -g @nestjs/cli
NestJS Application Creation Command:
nest new your-project-name

GraphQL NPM Packages:

Now run the following commands to install GraphQL packages required for our application.
1. npm i --save @nestjs/graphql
2. npm i --save graphql-tools
3. npm i --save graphql

Define GraphQL Schema:

GraphQL Schema is constructed by object types, most object types represent the domain object(domain object means a class or interface in an application that represents a table in the database). Query and Mutation are default object types of GraphQL Schema, these object types represent the operations like fetching or updating an API.

Now let's define GraphQL Schema object type that represents our application domain object as below.
src/student/student.grahpql(file extension *.grahql):
type Student{
    _id: String,
    FirstName: String,
    LastName: String,
    Standard: Int,
    FatherName: String,
    MotherName: String
  • The schema object type almost looks like a JSON object. 
  • The Schema object begins with 'type' keyword and 'Student' is the name we defined for the Schema object type. 
  • The Schema has a set of properties these must match with our domain object(class or interface in typescript represents a table in the database). 
  • GraphQL Schema has a set of pre-defined data types like 'Int', 'String', etc which looks similar to most of the programming language types.

Define GraphQL Schema Query Object Type:

The 'Query' object type is a default type in GraphQL Schema. 'Query' constructs all definitions to filter definitions of our API(simple words it contains all method definitions to filter and fetch data).

Let's define filter definitions for our 'Student' object type as below.
src/student/student.graphql(file extension *.graphql): 
type Query{
  • GraphQL Schema Query object holds all the definitions for filtering API. 
  • 'getAllStudents()' definition to fetch all data and [Student](name should match with our GraphQL Schema object type we defined in an earlier step) represents an array of 'Student' object types. 
  • 'getStudentById(id:string)' definition to fetch single object type with matched input value 'id'.

Import GraphQLModule:

In AppModule of our application, we need to register the GraphQLModule as below.
import { GraphQLModule } from '@nestjs/graphql';
import { join } from 'path';

  imports: [
      typePaths: ['./**/*.graphql'],
        path: join(process.cwd(),'src/graphql.schema.ts')
export class AppModule {}
// code hidden for display purpose
  • Inside import array registered 'GraphQLModule.forRoot({})' from '@nestjs/grahpql' library. 
  • 'GraphQLModule.forRoot({})' the module takes input configuration object with properties like 'typePaths', 'definitions'.
  • 'typPaths'  used to access all GraphQL Schema defined files and it takes collection of file paths as input. 
  • './**/*.graphql' defines folder paths to search for graphql files, './'(mostly represents 'src') root path, '/**/'  defines all folder and it subfolders, '*.graphql' all files inside the folders with '.graphl' file extension. 
  • 'definitions' takes an object which contains property like 'path', the use of this 'path' property to auto generate the typescript classes or interface based on the GraphQL object types. So for this 'path' property need specify location for '*.ts'(like 'src/grahql.schema.ts') generation.

Auto-Generated GraphQL Schema To Typescript Classes or Interfaces:

On application start, all the GraphQL Schema objects are collected and generates matching typescript classes or interface for build communication between typescript and GraphQL schema.

To check application start commands go to package.json file and check the scripts object inside it.
Development command to start the application:
npm run start:dev
On application started, the schema file gets crated as below.

On starting the application if the build fails as below
Then install the required package shown in the error above.
npm install apollo-server-express

Service Provider:

In general service provider contains logic to fetch the data from databases. Let's create a service provider with test data as follows.
import {Student} from '../graphql.schema';

export class StudentService {
            FirstName: "Naveen",
            LastName: "Bommidi",
            Standard: 7,
            FatherName: "Gopala Krishna",
            MotherName: "Mallikasulamma"
        }]; // while testing graphql api add more test data

        return this.students;

        var filteredStudent = this.students.filter(_ => _._id === id)[0];
        return filteredStudent;
'Student' type importing from auto-generated classes or interface based on the schema object type.

Now import service provider in app.module.ts file as follows.
import {StudentService} from './student/student.service';

  providers: [StudentService],
export class AppModule {}
// code hidden for display purpose


Resolver is used to implement the GraphQL operation like fetching or saving data, based on default schema object types like 'Query'(contains definition for filtering and fetching data) or 'Mutation'(contains definition for creating or updating data).

Let's resolve the 'Query' object type in 'student.graphql' file as below.
import { Resolver, Query, Args } from '@nestjs/graphql';
import { StudentService } from './student.service';
import { Student } from '../graphql.schema';

export class StudentResolver {
  constructor(private studentService: StudentService) {}

  getAllStudents(): Student[] {
    return this.studentService.getAllStudents();

  getStudentById(@Args('id') id: string):Student{
      return this.studentService.getStudentById(id);
  • '@Resolver()' imported from '@nestjs/graphql' package, it should be decorated over the class to make it resolver class and it takes optional string input parameter where we pass the name of the GraphQL schema object type(eg: Student). 
  • '@Query()' imported from '@nestjs/graphql', this decorator represents the 'Query' object type in GraphQL Schema and it should be decorated over the implemented methods of the 'Query' object type
  • '@Arg()' is capture the input values from the clients.
Now import the resolver into the app.module.ts file as follows. app.module.ts:
import { StudentResolver } from './student/student.resolver';

  providers: [StudentResolver],
export class AppModule {}
// hidden some code for display purpose

GraphQL UI Playground:

GraphQL UI Playground is the page which helps as a tool to query our GraphQL API (if we compare with REST API UI Playground is like Swagger). This Playground gives Schema information, GraphQL Documentation, Intelligence to type the queries more quickly. GraphQL constructed only one endpoint and supports only Http Post verb, so to access this UI Playground simply use same endpoint in the browser directly.


GraphQL is about asking for specific fields on objects on the server. Only requested fields will be served by the server.

Let's query a few fields from the 'Student' schema as follow.
  • 'query' keyword to identify the request is for fetching or querying data based on 'Query' Schema object at the server. 
  • 'getAllStudents' keyword to identify the definition or method inside of the 'Query' schema object. 
  • 'FirstName', 'LastName' are fields inside of the 'Student' GraphQL object type we created. 
From the above result image, API returns only requested fields and the definition or method name used as the response object name(eg: 'getAllStudents' returned response as an array of objects).

Input Arguments To Filter Data:

In GraphQL we can pass arguments to filter the Data. Let's construct the query as below with a filtering argument.
In 'Query' object type we have a definition 'getStudentById' which takes an input parameter, the above query is to execute this definition.


While querying the GraphQL API with schema definition names like 'getAllStudents', 'getStudentById' are more self-explanatory, which good for requesting the API. But API on returning a response uses the same definition name as main object name which looks bit different naming convention for JSON response object. In GraphQL to overcome this scenario, we can use 'Aliases' names which are defined by the client, the API will serve the response with those names.
Here 'Student' is the alias name for 'getAllStudents'.


Fragments in GraphQL API mean comparison between two or more records. A comparison between 2 or more items is very easy in GraphQL.
Defining a schema definition payload multiple times inside of the query object is called Fragments. The fragment is only possible between the same type of schema definition if you try to execute between different schemas that lead to error. In each definition you can define any number of field names, it is not mandatory to define the same number field names in all definitions as in the above query.


GraphQL Mutation object type deals with data updates. All the definitions in the Mutation object type have the responsibility of saving or updating the data to storage (like a database).

For saving data in the Mutation object type definition we need to pass an argument that should be an object. In GraphQL Schema to create an argument object, we need to construct an object type as follows.
input StudentInput{
    FirstName: String,
    LastName: String,
    Standard: Int,
    FatherName: String,
    MotherName: String
Object type constructed with 'input' keyword is used for argument variable type for the definitions either in 'Query' or 'Mutation' object types.

Let's define the Schema definition in Mutation object type as follows
type Mutation{
'StudentInput' is used to input argument for creating definitions.
You can't use 'Student' object type as an argument type in 'create' definition, because in graphql object get created by using 'input' keyword to use as an argument type.
Let's update the service provider class as follows.
import {Student} from '../graphql.schema';

export class StudentService {
 // code hidden for display purpose
        return newStudent;

Let's now update the resolver class by implementing the 'create' definition in the Mutation object type as follows.
import {Args, Mutation } from '@nestjs/graphql';
import { StudentService } from './student.service';
import { Student, StudentInput } from '../graphql.schema';

export class StudentResolver {
  constructor(private studentService: StudentService) {}

    return this.studentService.createStudent(student);
In resolve class, while implementing the definition in 'Mutation' object type then we need to use '@Mutation()' decorator on top of the implemented method. 'StudentInput' class which auto-generated from GraphQL Schema to 'src/graphql-schema.ts' file.

Now to create GraphQL query to save a new item as follows
  "student": {
    "_id": "abc4",
    "FirstName": "Rohit",
    "LastName": "Sharma",
    "Standard": 10,
    "FatherName": "Jagadesh",
    "MotherName": "Lalitha"
This is a way to send data to save in graphql,  "student" in JSON object must match with the name with an input parameter of 'create()' method which means  'student' is GraphQL variable.
Test the new item added by using a query as follow.

Wrapping Up:

Hopefully, this article will help to understand the GraphQL API integration in the NestJS application using Schema First Approach. I love to have your feedback, suggestions, and better techniques in the comment section.


Follow Me:


Post a Comment

Popular posts from this blog

Endpoint Routing In Asp.Net Core

How Routing Works In  Core 2.1 And Below Versions?: In Asp.Net Core routing is configured using app.UseRouter() or app.UseMvc() middleware. app.UseMvc(routes => { routes.MapRoute( name: "default", template: "{controller=Home}/{action=Index}/{id?}"); }); Here in Dotnet Core version 2.1 or below versions on the execution of route middleware request will be navigated appropriate controller matched to the route.

An operation or functionality which is dependent on route URL or route values and that need to be implemented before the execution of route middleware can be done by accessing the route path from the current request context as below
app.Use(async (context, next) => { if(context.Request.Path.Value.IndexOf("oldvehicle") != -1) { context.Response.Redirect("vehicle"); } else { await next(); } }); app.UseMvc(routes => { routes.MapRoute( name: "vehicleRoute", template: "vehicle", defaults:new { …

GraphQL API Integration In Asp.Net Core Application

GraphQL is a query language for your API and a server-side runtime for executing queries by using a type system you define for your data. GraphQL can be integrated into any framework like ASP.NET, Java, NestJs, etc and it isn't tied to any specific database or storage engine and is instead backed by your existing code and data.
How GraphQL API Different From Rest API: GraphQL exposes a single end-point or route for the entire application, regardless of its responses or actions.HTTP-POST is the only Http verb recommended by the GraphQL.The client applications (consumers of API) can give instructions to GraphQL API about what type of properties to be returned in the response. Building Blocks Of GraphQL API:The main building blocks of GraphQL API is Schemas and Types. A 'Schema' in GrpahQL API describes the functionality available to the clients connect to API. Schema mostly consists of GraphQL Object Types, Queries, Mutations, etc.Types likely to be called Grap…

ASP.NET Core Web API Versioning

Introduction: An iteration and evolutionary changes of an ASP.NET Core Web API is handled by Versioning. Versioning of an API gives confidence to the clients which consumes API for a long time. Any changes or development of an API will be accessible using the new version and it won't cause issues to the clients consuming the old version of API.
When To Use Versioning:Any API response changes.Developing an API by implementing testing levels like 'Alpha', 'Beta', and 'RC' versions before releasing Production.Deprecating an API which means API going to be removed or upgraded by a version within a short period. Versioning Types:Query String VersioningUrl Path VersioningMedia Type Versioning API Version Nuget: To Configure versioning to AspNet Core Web API Microsoft provided a library(Microsoft.AspNetCore.Mvc.Versioning). So to use the versioning library please install NuGet below.
 Install-Package Microsoft.AspNetCore.Mvc.Versioning -version 4.0.0 Register API V…

.NET Core MVC Application File Upload To Physical Location With Buffered Technique

Buffering Technique In File Upload:The server will use its Memory(RAM) or Disk Storage to save the files on receiving a file upload request from the client. Usage of Memory(RAM) or Disk depends on the number of file requests and the size of the file. Any single buffered file exceeding 64KB is moved from Memory to a temp file on disk. If an application receives heavy traffic of uploading files there might be a chance of out of Disk or RAM memory which leads to crash application. So this Buffer technique used for small files uploading. In the following article, we create a sample for the file uploading using .NET Core MVC application.
Create The .NET Core MVC Project: Let's create a .NET Core MVC project, here for this sample I'm using Visual Studio Code as below.  Check the link to use the Visual Studio Code for .NET Core Application.
IFormFile: Microsoft.AspNetCore.Http.IFormFile used for file upload with buffered technique. On uploading files from the client, then the entire …

Ionic Picker Sample Code In Angular

Introduction: Ionic Picker(ion-picker) is a popup slides up from the bottom of the device screen, which contains rows with selectable column separated items.
The main building block of ion-picker as follows: PickerControllerPickerOptions PickerController: PickerController object helps in creating an ion-picker overlay. create(opts?: Opts): Promise<Overlay> PickerController create method helps in create the picker overlay with the picker options
PickerOptions: PickerOptions is a configuration object used by PickerController to display ion-picker.
Single Column Ionic Picker: single.item.picker.ts: import { Component } from "@angular/core"; import { PickerController } from "@ionic/angular"; import { PickerOptions } from "@ionic/core"; @Component({ selector: "single-column-picker", templateUrl:"single.item.picker.html" }) export class SingleItemPicker { animals: string[] = ["Tiger", "Lion", "Elephant"…

Asp.Net Core MVC Form Validation Techniques

Introduction: Form validations in any applications are like assures that a valid data is storing on servers. All programing frameworks have their own individual implementations for form validations. In Dotnet Core MVC application server-side validations carried on by the models with the help of Data Annotations and the client-side validations carried by the plugin jQuery Unobtrusive Validation. jQuery Unobtrusive Validation is a custom library developed by Microsoft based on the popular library jQuery Validate.
In this article, we are going to learn how the model validation and client-side validation works in Asp.Net Core MVC Application with sample examples.
Getting Started: Let's create an Asp.Net Core MVC application project using preferred editors like Microsoft Visual Studio or Microsoft Visual Studio Code. Here I'm using Visual Studio.
Let's create an MVC controller and name it as 'PersonController.cs' and add an action method as below.
PersonController.cs: us…

Blazor WebAssembly Dynamic Form Validation

Introduction: In Blazor WebAssembly(client-side framework) form validation can be done with Data Annotations. Using Data Annotations we can validate form either by default validation attributes or by creating custom validation attributes. Using this Data Annotation attribute we can dynamically add or remove validation on a specific field in a form.
Create Blazor WebAssembly Project: To create a Blazor WebAssembly template project need to install the latest version of VisualStudio 2019 for rich intelligence support or we can use VisualStudio code but less intelligence support from the editor. Click here to know about Blazor WebAssembly template creation. Blazor WebAssembly is in preview mode, not yet ready for production.
Create Razor Component: After creating a sample project using the Blazor WebAssembly template, in "Pages" folder add new Razor Component, name it as "UserForm.razor"
Add Route: In Blazor routing can be configured using @page  directive, and URL should b…

Blazor Server CRUD Operations

Introduction: Blazor Server is a web framework to develop server-side single-page applications. Blazor is made up of components with the combinations on C#, Html, CSS.  Blazor Server is production-ready from the .Net Core 3.0.  Blazor Server Working Mechanism:Blazor Server is a very light-weight web development framework. In Blazor Server, not all code gets downloaded to the client browsers. Blazor Server made of components these components can be a block of code or page with respective navigation. Blazor server application communicates with the server with a SignalR background connection which is inbuilt functionality. Application click,  form submission, change events, application page navigation every operation is carried out by the SignalR connection by communicating with the server. Blazor updates the Html DOM very gently on every data update without any overhead. Blazor Server application maintains a nice intelligent tree structure to update the required information or changed …

NestJS API CRUD Operations With MongoDB

Introduction: NestJS is a framework used to develop server-side applications. NestJS built on top of Node.js frameworks like Express. It is a combination of Progressive Javascript, Object-Oriented Programming, Functional Programming, and Functional Reactive Programming.
Nest CLI Installation: Using Nest CLI we are able to generate the NestJS starter project with the default template. To install Nest CLI globally over our system open command prompt and run the command
npm i -g @nestjs/cli Now create a sample project by using Nest CLI command  nest new your_project_name package.json: Now open the package.json file from the sample application created, you can observe few properties like "scripts", "dependencies", and "devDependencies".
"dependencies" contains all plugins to be installed and used them to run the application.
"devDependencies" contain all plugins to be installed and used them at the time of application development.

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-ControlPragmaVary 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 - this directive represents no storing of response and always fetch the fresh response from serverno-store…