NGraphQL is a framework for implementing GraphQL APIs in .NET. It provides server- and client-side components.
Here is an overview of the project, what is different and why I created it in the first place.

• Conforms to GraphQL Specification, Oct 2021 Edition.
• GraphQL model is defined using plain c# (POCO) classes decorated with some attributes. Unlike other .NET GraphQL solutions, NGraphQL-based API definitions look and feel like real .NET artifacts - strongly typed, compact and readable.
• Server and client components. ASP.NET Core -based HTTP server implementation following the standard "serving over HTTP" rules
• Light-weight but capable GraphQL Client - supports both dynamic-type objects for return data, or strongly-typed objects by directly using the GraphQL c# classes from the model.
• Modular construction - separately coded modules define parts of the overall GraphQL API Schema; modules are registered with the GraphQL host server which implements the GraphQL API.
• Parallel execution of Query requests
• Sync and Async resolver methods
• Full Introspection support
• Schema descriptions are automatically imported from XML comments in c# code
• Full support for fragments and standard directives (@include, @skip, @deprecated)
• Custom Scalars out of the box (Double, ID, Uuid, DateTime etc)
• Fast, efficient query parser; query cache - parsed queries are saved in cache for future reuse with different input variables
• Facilities for input validation and returning failures as multiple GraphQL errors
• Robust implementation of batching (N+1 problem)
• Integration with relational databases and ORMs - the BookStore Sample shows a GraphQL server on top of a data-connected application, with batching support.
• Built-in logging and diagnostics, query timings and metrics

NGraphQL binaries are distributed as a set of NuGet packages:

The repo contains a TestApp with HTTP server and Graphiql UI. It is used in HTTP server harness and unit tests. It is a made-up GraphQL API about abstract Things, and it is void of any real semantic meaning. The sole purpose of this app is to provide a number of types and methods covering the many aspects of the GraphQL protocol. Run the HTTP server harness and play with the Graphiql page in browser.

Run the unit tests and see the many request/response examples used there. The unit tests write a detailed log as they go. Run the tests, locate the log file in the bin folder, and look inside for many examples of GraphQL requests and responses along with the metrics. See this file here: UnitTestsLog.

See also Star Wars Example in a separate github repository.

VITA ORM contains a sample project implementing a GraphQL Server for a BookStore sample application. Among other things, it shows how (N+1) problem can be efficiently handled automagically by a smart-enough ORM. Most of the related entities like Book.Publisher or Book.Authors are batch-loaded automatically by the ORM.

See the Wiki pages for this project.

• Code-first only, no schema-first scenario. Implementing a working GraphQL API requires creating a number of detailed c#/.NET artefacts that cannot be directly derived from the Schema document. The complete schema-first scenario is not feasible.

• Subscriptions are not supported directly, only at GraphQL parsing/invocation level. The actual bi-directional channel (websockets) is expected to be implemented in a separate library. A sample and a reference implementation is planned in the future.

Visual Studio 2022+, .NET Standard 2.0, fully compatible with .NET 5, 6 and up.

• GraphQL DotNet
• HotChocolate
• Tanka GraphQL