Cephalon.AspNetCore.GraphQL
Maturity:
M2· Ownership: cephalon-managed · Family:transport-adapter· See audit, matrix.
Cephalon.AspNetCore.GraphQL adds GraphQL transport support to the ASP.NET Core host.
What it owns
Section titled “What it owns”- GraphQL server registration through Hot Chocolate
- module marker contract for GraphQL-capable Cephalon modules
- shared query, mutation, and subscription root contribution helpers for module
ConfigureServices(...) - separate built-in GraphQL HTTP, schema, GraphQL-over-SSE, and GraphQL-over-WebSocket endpoint mapping under the ASP.NET Core transport surface
Main surfaces
Section titled “Main surfaces”Hosting/GraphQLTransportServiceCollectionExtensions.csModules/IGraphQLModule.csRouting/GraphQLTransportRouteMapper.cs
Source structure
Section titled “Source structure”HostingModulesRouting
How it fits
Section titled “How it fits”Use this package when a host selects the GraphQL transport. The engine still owns transport
selection and runtime introspection; this package only makes that choice executable on ASP.NET Core
and gives modules a transport-specific place to contribute schema types.
Modules can now stay on the shared Cephalon GraphQL authoring path for all three schema roots by
calling ConfigureGraphQLQuery(...), ConfigureGraphQLMutation(...), and
ConfigureGraphQLSubscription(...) from ConfigureServices(...). Modules or hosts that expose
subscription fields still need to register a concrete Hot Chocolate subscription provider, such as
AddInMemorySubscriptions(), through ConfigureGraphQLTransport(...) so the built-in
GraphQL-over-SSE and GraphQL-over-WebSocket routes can execute real subscription traffic instead of
only shaping the schema.
The built-in host surface now keeps the GraphQL protocols explicit while still following the shared
ApiRoutes:Prefixes contract. By default the package maps GraphQL HTTP at /graphql, the schema
document at /graphql/schema, GraphQL-over-SSE at /graphql-sse, and GraphQL-over-WebSocket at
/graphql-ws. Those routes also participate in the same ASP.NET Core rate-limiting catalog, so
/engine/rate-limiting can describe them truthfully as request-response, long-lived stream, or
long-lived connection surfaces instead of flattening them into one generic GraphQL label.
The hosting coverage now also proves those routes through real protocol behavior: custom schema
prefixes resolve SDL downloads correctly, the SSE route produces text/event-stream, and the
WebSocket route executes the graphql-transport-ws handshake plus next / complete frames.