GraphQL API with ASP.NET Core and Hot Chocolate is a course in building GraphQL APIs with C# on .NET 10 and Hot Chocolate, from schema design and SQL Server access with EF Core and DataLoader to mutations, subscriptions and API protection. It suits C# and ASP.NET Core developers who build APIs for websites and mobile apps.
GraphQL lets client applications ask for exactly the data they need in a single call, through one endpoint backed by a strongly typed schema, which makes it a good fit for systems where websites, mobile apps and several services share the same data. On .NET the most widely used tool is Hot Chocolate, which turns C# classes and methods into a GraphQL schema automatically and ships with Nitro, a built-in IDE for testing queries.
This course teaches how to build GraphQL APIs with ASP.NET Core on .NET 10 and Hot Chocolate 16. Learners start with the query language and schema design, connect to SQL Server with EF Core 10, solve the N+1 problem with DataLoader, add paging, filtering and sorting, write mutations and subscriptions, add authentication and authorisation, protect the API from overly expensive queries, call it from a client with Strawberry Shake, and finish by testing and deploying with Docker. (3 days, 6 hours per day, 18 hours in total, Intermediate level.)
Course Details
This course is the 2026 edition of GraphQL API with ASP.Net 6, rewritten for .NET 10 (LTS), ASP.NET Core 10, EF Core 10 and Hot Chocolate 16. It runs for 3 days, 6 hours per day (18 hours in total, 09:00-16:00), as lectures with labs built around a sample shop system that grows throughout the course. Intermediate level. Day one covers the query language and schema design, day two connects to SQL Server with EF Core 10 and adds DataLoader, paging, filtering and mutations, and day three covers subscriptions, authorisation, protection against expensive queries, a Strawberry Shake client, and testing and deployment with Docker. All classroom tools are free, and learners take home the source code for every lab.
Section 1: What GraphQL Is and Where It Fits
Section 2: Lab: Setting Up .NET 10 and a Hot Chocolate Project
Section 3: Lab: The GraphQL Query Language
Section 4: Schemas and the Type System
Section 5: Lab: Implementation-First Schemas
Section 6: Lab: Connecting to SQL Server with EF Core 10
Section 7: Lab: DataLoader and the N+1 Problem
Section 8: Lab: Paging, Filtering, Sorting and Projection
Section 9: Lab: Mutations and Input Types
Section 10: Error Handling and Validation
Section 11: Lab: Real-Time Subscriptions
Section 12: Lab: Authentication and Authorisation
Section 13: Protecting the API from Expensive Queries
Section 14: Lab: Calling the API from a Client
Section 15: Workshop: Testing, Monitoring and Deployment
No public rounds are open right now. Join the waiting list and we will contact you first when the next round opens, or ask us on LINE. Or call 02-570-8449 or 088-807-9770
REST exposes a separate endpoint for each resource, and each returns a fixed shape of data, so clients often get too much or too little and need several calls. GraphQL uses a single endpoint where the client writes a query naming exactly the fields it needs, including nested data, and gets it in one request. A strongly typed schema acts as the contract between client and server. In practice many organisations run both side by side.
A query only reads data, much like GET in REST. A mutation creates, updates or deletes data and can return the changed result in the same call. A subscription lets the client receive data in real time when something happens on the server, such as a new order, usually over a WebSocket connection. When Hot Chocolate runs on several instances, Redis is commonly used to carry the events between them.
Install the Hot Chocolate templates and create a project with dotnet new graphql on .NET 10. Set up EF Core 10 with models, a DbContext and migrations, then register a DbContext factory alongside AddGraphQLServer in Program.cs. Write a query class using attributes such as [QueryType] so the source generator builds the schema, map the /graphql endpoint with MapGraphQL and test it in Nitro before adding DataLoader, paging, mutations and subscriptions.
It suits C# and ASP.NET Core developers who want to build APIs with GraphQL, backend developers who need to serve many kinds of client, and teams on older GraphQL setups for .NET who want to update. You should be able to write C#, understand classes, async/await and basic LINQ, have built a website or web API with ASP.NET Core, and know basic SQL.
You will be able to write queries with arguments, aliases, fragments, variables and directives, design schemas with Hot Chocolate 16 on .NET 10, read SQL Server data with EF Core 10 and DataLoader, implement paging, filtering, mutations and subscriptions, protect the API with authorisation and cost analysis, call it with Strawberry Shake and deploy it with Docker. Participants who complete the training receive a Certificate of Completion with its own number, which can be verified online.
Yes. It can be run in-house for your team, with examples adapted to your own work, such as designing the schema around the databases or systems your team already maintains, or planning the move of an existing GraphQL server to .NET 10. You can request a quotation from this page, or contact us on LINE @itgenius or by phone on 02-570-8449.
Articles are published in Thai.
Once you can write C# comfortably, what separates professional code from code that merely works is a deeper grasp of how the language behaves: flexible object-oriented design, memory management, generics, delegates and LINQ, and asynchronous and multithreaded…
Microservices split a large system into smaller services that can be developed, deployed and scaled independently. Each service owns its database and talks to others through APIs or messages. Teams can work in parallel and change one part at a time, but this…
Modern web applications usually separate the frontend from the backend: the backend exposes a Web API and the frontend is a single page application that calls it. ASP.NET Core on .NET 10 (LTS) is a robust choice for enterprise APIs and runs on Windows, macOS…
