Skip to main content

A Basic GraphQL CRUD Operation With .NET6 + Hot Chocolate(V 12) + SQL Database

In this article, we are going to implement GraphQL CRUD operation in .NET6, Hot Chocolate(V12), SQL Database.

GraphQL:

GraphQL is an open-source data query and manipulation and language for APIs. It 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 .NET, Java, NestJS, etc and it isn't tied to any specific database or storage engine and is backed by your existing code and data.

GraphQL 2 main operations are like:
  • Query(fetching data)
  • Mutation(data manipulation like save, update, delete)

Hot Chocolate GraphQL:

Hot Chocolate is an open-source GraphQL server that is compliant with the newest GraphQL latest specs. It is the wrapper library of the original .NET GraphQL library. Hot Chocolate takes the complexity away from building a fully-fledged GraphQL server.

Create A .NET6 Web API Project:

Let's create a .Net6 Web API sample application 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.
.NET CLI Command:
dotnet new webapi -o Your_Project_Name

Install Entity Framework Core NuGet:

Now install the entity framework core NuGet.
Package Manager Command:
Install-Package Microsoft.EntityFrameworkCore -Version 6.0.1

.Net CLI Command:
dotnet add package Microsoft.EntityFrameworkCore --version 6.0.1

Now install SQL library which dependant on entity framework core NuGet.
Package Manager Command:
Install-Package Microsoft.EntityFrameworkCore.SqlServer -Version 6.0.1

.Net CLI Command:
dotnet add package Microsoft.EntityFrameworkCore.SqlServer --version 6.0.1

SQL Query To Create A Sample Table:

Run the below command to the sample table.
CREATE TABLE [dbo].[Cake] (
    [Id]          INT             IDENTITY (1, 1) NOT NULL,
    [Name]        VARCHAR (MAX)   NULL,
    [Price]       DECIMAL (18, 2) NULL,
    [Description] VARCHAR (MAX)   NULL
);

Setup Entity Framework Core DatabaseContext:

Let's create a class that represents our table. So let's create folders like 'Data' and subfolders like 'Entities' and then add a class like 'Cake.cs'
Data/Entities/Cake.cs:
namespace Dot6.HotChoco12.GraphQL.CRUD.Demo.Data.Entities;
public class Cake
{
    public int Id { get; set; }
    public string Name { get; set; }
    public decimal Price { get; set; }
    public string Description { get; set; }
}
To manage or control all the table classes we have to create DatabaseContext class. So let's create our context class like 'MyWorldDbContext.cs' in the 'Data' folder.
Data/MyWorldDbContext.cs:
using Dot6.HotChoco12.GraphQL.CRUD.Demo.Data.Entities;
using Microsoft.EntityFrameworkCore;

namespace Dot6.HotChoco12.GraphQL.CRUD.Demo.Data;

public class MyWorldDbContext : DbContext
{
    public MyWorldDbContext(DbContextOptions<MyWorldDbContext> options) : base(options)
    {
 
    }
    public DbSet<Cake> Cake { get; set; }
}
  • (Line: 6) The 'Microsoft.EntityFrameworkCore.DbContext' needs to be inherited by our 'MyWorldDbContext' to act as a Database context class.
  • (Line: 8) The 'Microsoft.EntityFrameworkCore.DbContextOptions' is instance of options that we are going to register in 'Program.cs' like 'ConnectionString', 'DatabaseProvider', etc.
  • (Line: 12) All our table classes must be registered inside of our Database context class with 'DbSet<T>' so that the entity framework core can communicate with tables of the database.
In the 'appsettings.Development.json' file add the connection string.
appsettings.Development.json:
"ConnectionStrings":{
    "MyWorldDbConnection":"your_connection"
}
Register the Database Context service in the 'Program.cs' file for the dependency injection.
builder.Services.AddDbContext<MyWorldDbContext>(options =>
{
	options.UseSqlServer(builder.Configuration.GetConnectionString("MyWorldDbConnection"));
});

Install Hot Chocolate NuGet:

Let's install the Hot Chocolate NuGet Package.
Package Manager Command:
Install-Package HotChocolate.AspNetCore -Version 12.6.0

.NET CLI Command:
dotnet add package HotChocolate.AspNetCore --version 12.6.0

Configure GraphQL Service And Endpoint:

Now let's register the GraphQL service into the 'Program.cs'.
Program.cs:
builder.Services.AddGraphQLServer();
Now let's register the GraphQL endpoint into the 'Program.cs'.
Program.cs:
app.MapGraphQL();

Read Operation:

In GraphQL fetching data can be called 'Query'. Let's frame GraphQL 'Query' to read the data from the server.

Let's create 'Query' entity like 'QueryType.cs'. Add resolver method that returns a collection of data. In GraphQL 'Resolver' is a method that contains logic to return the response to the users. So let's create a new folder like 'GqlTypes' inside of it add 'QueryType.cs'.
GqlTypes/QueryType.cs:
using Dot6.HotChoco12.GraphQL.CRUD.Demo.Data;
using Dot6.HotChoco12.GraphQL.CRUD.Demo.Data.Entities;
using Microsoft.EntityFrameworkCore;

namespace Dot6.HotChoco12.GraphQL.CRUD.Demo.GqlTypes;

public class QueryType
{
    public async Task<List<Cake>> AllCakesAsync([Service] MyWorldDbContext context) 
    { 
        return await context.Cake.ToListAsync();
    }
}
  • Here QueryType is plain c# class.
  • The 'AllCakesAsync' method is 'Resolver'. The GraphQL resolvers are logic units that return responses to the user.
  • (Line: 9) Injected our database context into our resolver method as an input parameter. The 'HotChocolate.Service' attribute helps for the context injection at the scope level.
  • (Line: 11) Returning collection of results from the database.
Register our Query entity(QueryType) into the Program.cs
Program.cs:
builder.Services
.AddGraphQLServer()
.AddQueryType<QueryType>();
Sample query for fetching the data:
query{
   allCakes{
     id
     name
   }
}
  • (Line: 1) The 'query' GraphQL keyword to specify this is a read operation.
  • (Line: 2) Our c# resolver method name 'AllCakesAsync' so to invoke this resolver method, in GraphQL we have to call 'allCakes'(Lower camel casing, 'async' keyword can be ignored).
  • (Line: 3-4) Inside of the resolver method name we have to specify the properties names which we required, the server also returns only the requested properties. The property names also should follow the Lower camel case.
Now open the 'Banana Cake Pop' Hot Chocolate testing tool by navigation to 'https://localhost:[port-number]/grpahql'.

Create Operation:

In GraphQL saving or updating or deleting of data is called 'Mutation'. Let's frame a 'Mutation' to create a new into the database.

Let's create a 'Mutation' entity like 'MutationType.cs'. Add a resolver method that creates a new record into the database. So inside of the 'GqlType' folder let's add a mutation entity like 'MutationType.cs'.
GqlType/MutationType.cs:
using Dot6.HotChoco12.GraphQL.CRUD.Demo.Data;
using Dot6.HotChoco12.GraphQL.CRUD.Demo.Data.Entities;

namespace Dot6.HotChoco12.GraphQL.CRUD.Demo.GqlTypes;

public class MutationType
{
    public async Task<Cake> SaveCakeAsync([Service] MyWorldDbContext context,
    Cake newCake)
    {
        context.Cake.Add(newCake);
        await context.SaveChangesAsync();
        return newCake;
    }
}
  • Here 'MutationType' is a plain c# class.
  • Here 'SaveCakeAsync()' is a resolver method.
  • Here 1st parameter is our Database context, 2nd parameter is our new record that needs to be created.
  • (Line: 11-13) Here we are saving the new record into the database and then return the new record as a response.
Now register our 'MutationType' into the 'Program.cs'.
Program.cs:
builder.Services
.AddGraphQLServer()
.AddQueryType<QueryType>()
.AddMutationType<MutationType>();
Sample mutation to insert a new record:-
GraphQL Variable:
{
  "newCake": {
    "id": 0,
    "description": "Strawberry flavored cake",
    "name": "Strawberry Cake",
    "price": 75
  }
}
  • (Line: 2) The 'newCake' GraphQL variable name
  • (Line: 3-6) Our payload needs to be saved to the database.
Mutation:
mutation($newCake:CakeInput!){
  saveCake(newCake:$newCake) {
    id
  }
}
  • (Line: 1) The 'mutation' is Graphql keyword is specified for updating the data into the server. The '$newCake' is the GraphQL variable we defined above but here we need to append '$'. The 'CakeInput!'(non-nullable type), it is a GraphQL type that was generated based on our payload type at a server. At the server our input payload type is 'Cake',  so on the GraphQL side, its type looks like 'CakeInput'(So the convention is like 'Cake'(C# class name) + 'Input').
  • (Line: 2) The 'saveCake' is our resolver method name its naming convention is Lower Camel Case.
  • The 'nameCake' is a variable name the same as at the sever resolver method input parameter name.
  • (Line: 3) Requesting the newly created record id.

Update Operation:

The update operation is a GraphQL mutation. Let's create a new resolver method for updating the record.
GqlType/MutationType.cs:
public async Task<Cake> UpdateCakeAsync([Service] MyWorldDbContext context, Cake updateCake)
{
	context.Cake.Update(updateCake);
	await context.SaveChangesAsync();
	return updateCake;
}
  • Here is our mutation resolver method for updating the record to the database.
Sample mutation to update the record:
Variable:
{
  "updateCake": {
    "id": 16002,
    "description": "Strawberry flavored Sugar cake",
    "name": "Strawberry Cake",
    "price": 85
  }
}
  • Here 'updateCake' is the name of our GraphQL variable. Here we must have the 'id' value for updating the record.
Mutation:
mutation($updateCake:CakeInput!){
  updateCake(updateCake:$updateCake) {
    id
    description
    name
    price
  }
}

Delete Operation:

The delete operation is GraphQL Mutation. Let's add a new resolver method for deleting the record.
GqlType/MutationType.cs:
public async Task<string> DeleteCakeAsync([Service] MyWorldDbContext context, int id)
{
	var cakeToDelete = await context.Cake.FindAsync(id);
	if (cakeToDelete == null)
	{
		return "Invalid Operation";
	}
	context.Cake.Remove(cakeToDelete);
	await context.SaveChangesAsync();
	return "Record Deleted!";
}
  • Here we passing 'id' as input parameter for our resolver method 'DeleteCakeAsync()'.
  • (Line: 3) Fetching the record from the database.
  • (Line: 4-7) Checking the record to be deleted exist in the database or not.
  • (Line: 8-9) Deleting the record from the database.
Sample mutation to delete the record:
Variable:
{
  "id":16002
}
  • Here 'id' GraphQL variable name.
Mutation:
mutation($id:Int!){
  deleteCake(id:$id)
}
  • Here 'Int!' non-nullable Integer of GraphQL type.

Support Me!
Buy Me A Coffee PayPal Me

Video Session:

Wrapping Up:

Hopefully, I think this article delivered some useful information on a basic CRUD operation in Hot Chocolate(V12) GraphQL in .Net6. using I love to have your feedback, suggestions, and better techniques in the comment section below.

Refer:

Follow Me:

Comments

Popular posts from this blog

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'

.NET 7 Web API CRUD Using Entity Framework Core

In this article, we are going to implement a sample .NET 7 Web API CRUD using the Entity Framework Core. Web API: Web API is a framework for building HTTP services that can be accessed from any client like browser, mobile devices, and desktop apps. In simple terminology API(Application Programming Interface) means an interface module that contains programming functions that can be requested via HTTP calls either to fetch or update 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 the REST full services. Install The SQL Server And SQL Management Studio: Let's install the SQL server on our l

ReactJS(v18) JWT Authentication Using HTTP Only Cookie

In this article, we will implement the ReactJS application authentication using the HTTP-only cookie. HTTP Only Cookie: In a SPA(Single Page Application) Authentication JWT token either can be stored in browser 'LocalStorage' or in 'Cookie'. Storing the 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 the authentication with HTTP-only JWT cookie then we no need to implement the 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 authenticate our client application with JWT HTTP-only cookie, I developed a NetJS(which is a node) Mock API. Check the GitHub link and read the document on G

.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

Angular 14 State Management CRUD Example With NgRx(14)

In this article, we are going to implement the Angular(14) state management CRUD example with NgRx(14) NgRx Store For State Management: In an angular application to share consistent data between multiple components, we use NgRx state management. Using NgRx state helps to avoid unwanted API calls, easy to maintain consistent data, etc. The main building blocks for the NgRx store are: Actions - NgRx actions represents event to trigger the reducers to save the data into the stores. Reducer - Reducer's pure function, which is used to create a new state on data change. Store - The store is the model or entity that holds the data. Selector - Selector to fetch the slices of data from the store to angular components. Effects - Effects deals with external network calls like API. The effect gets executed based the action performed Ngrx State Management flow: The angular component needs data for binding.  So angular component calls an action that is responsible for invoking the API call.  Aft

Angular 14 Crud Example

In this article, we will implement CRUD operation in the Angular 14 application. Angular: Angular is a framework that can be used to build a single-page application. Angular applications are built with components that make our code simple and clean. Angular components compose of 3 files like TypeScript File(*.ts), Html File(*.html), CSS File(*.cs) Components typescript file and HTML file support 2-way binding which means data flow is bi-directional Component typescript file listens for all HTML events from the HTML file. Create Angular(14) Application: Let's create an Angular(14) application to begin our sample. Make sure to install the Angular CLI tool into our local machine because it provides easy CLI commands to play with the angular application. Command To Install Angular CLI npm install -g @angular/cli Run the below command to create the angular application. Command To Create Angular Application ng new name_of_your_app Note: While creating the app, you will see a noti

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

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

ReactJS(v18) Authentication With JWT AccessToken And Refresh Token

In this article, we are going to do ReactJS(v18) application authentication using the JWT Access Token and Refresh Token. JSON Web Token(JWT): JSON Web Token is a digitally signed and secured token for user validation. The JWT is constructed with 3 important parts: Header Payload Signature Create ReactJS Application: Let's create a ReactJS application to accomplish our demo. npx create-react-app name-of-your-app Configure React Bootstrap Library: Let's install the React Bootstrap library npm install react-bootstrap bootstrap Now add the bootstrap CSS reference in 'index.js'. src/index.js: import 'bootstrap/dist/css/bootstrap.min.css' Create A React Component 'Layout': Let's add a React component like 'Layout' in 'components/shared' folders(new folders). src/components/shared/Layout.js: import Navbar from "react-bootstrap/Navbar"; import { Container } from "react-bootstrap"; import Nav from "react-boot

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