PrimeForgePrimeForgeOperations Desk
ops@primeforge:~/topology/dispatch$▍step 1 / 5
GraphQLForge · Federated Dispatch

Anatomy of a Query

Five beats that turn a single GraphQL document into a fan-out of subgraph requests and back into a unified response. Step through to see what lights up at each stage of the pipeline.

interactive walkthrough
gatewayclientqueryparse · validateschema ownershipdag plannercircuit breakerbatch 2hr-subgraphemployee datacompliancestatus datapayrollpayslip datapersonnelorg dataresp. mergeentity stitchunify · returnJSONbatch 1 · parallelbatch 2 · dependent
01
step 1 of 51

Query arrives at the gateway

The client sends a GraphQL query over HTTPS. Caddy terminates TLS and forwards to the gateway port. OnePass validates the JWT bearer token — checking signature, expiry, and RBAC claims — before any subgraph is contacted. An invalid or expired token is rejected here with a 401; the subgraph layer never sees it.

trace · step 016L
POST /graphql  HTTP/1.1
Authorization: Bearer eyJhbGci...
Content-Type: application/json

{ employee { name payslips { amount } department }
  complianceStatus }