Apollo GraphOS
API gatewayapollo-graphos
Hosted schema registry and router serving a federated GraphQL supergraph.
- Provider
- default
- Kind
- API gateway
- Category
- Edge
- Official docs
- https://www.apollographql.com/docs/graphos
| property | type | values | required | kind default | this component |
|---|---|---|---|---|---|
| auth | enum | none | api-key | jwt | oauth2 | mtls | no | none | ▸ none |
| concurrencyLimit | boolean | — | no | false | inherited |
| federation | boolean | — | no | true | inherited |
| idempotencyKeys | boolean | — | no | false | inherited |
| instances | integer | — | no | — | inherited |
| keyTtlHours | integer | — | no | — | inherited |
| managed | boolean | — | no | false | ▸ true |
| protocol | enum | http | grpc | websocket | fix | ouch | no | http | ▸ http |
| rateLimiting | boolean | — | no | false | ▸ false |
| routerHosting | enum | cloud | self-hosted | no | cloud | inherited |
| schemaChecks | boolean | — | no | true | inherited |
| tls | boolean | — | no | true | inherited |
Every rule whose selector covers this component's kind or its category. Whether a rule fires depends on the design: its properties, its edges and its groups.
sync-chain-too-deep
Every consecutive synchronous hop from this entry point spends part of the stated p95 latency budget, and the chain's failures multiply. More than three hops is a budget nobody is tracking.
- — all of these hold:
- — the design requirement `latency.p95Ms` has a value
- — the longest chain of synchronous calls starting at the node is more than 3 hops long
nodes:
- { id: "apollo-graphos", component: "apollo-graphos" }API Gatewayalibaba-api-gatewayAmazon API Gatewayaws-api-gatewayAWS AppSync GraphQL APIaws-appsyncAzure API Managementazure-api-managementAI Gatewaycloudflare-ai-gatewayCloudflare API Shieldcloudflare-api-shieldMCP Server Portalcloudflare-mcp-portalCloudflare Privacy Gatewaycloudflare-privacy-gatewayGeneric API gatewayapi-gatewayApache APISIXapisixEasegresseasegressEmissary-ingressemissaryEnvoy Gatewayenvoy-gatewayGloo GatewayglooHasurahasuraHelicone AI Gatewayhelicone-gatewayHigresshigressKong GatewaykongKong AI Gatewaykong-ai-gatewayKong Konnectkong-konnectKrakenDkrakendLiteLLM ProxylitellmMartian GatewaymartianNot Diamondnot-diamondPortkey AI GatewayportkeyRequestyrequestySpring Cloud Gatewayspring-cloud-gatewayTyk GatewaytykUnifyunify-aiVercel AI Gatewayvercel-ai-gatewayWSO2 API Managerwso2-api-managerZuulzuulApigeeapigeeAgent Gatewaygoogle-agent-gatewayAPI Gatewaygoogle-api-gatewayApigee hybridgoogle-apigee-hybridCloud Endpointsgoogle-cloud-endpointsFirebase Data Connectgoogle-firebase-data-connectIBM API Connectibm-api-connectOCI API Gatewayoci-api-gateway
# yaml-language-server: $schema=../../schema/component.schema.json # Apollo GraphOS: hosted schema registry and supergraph platform whose Router serves a federated # GraphQL API over subgraph services. Per the GraphOS documentation the router runs either as a # GraphOS-hosted cloud router or self-hosted next to the subgraphs, fetching its schema from the # registry. schemaVersion: "1" type: "component" id: "apollo-graphos" kind: "api-gateway" provider: "default" docs: "https://www.apollographql.com/docs/graphos" defaults: managed: true auth: "none" rateLimiting: false protocol: "http" properties: routerHosting: type: "enum" values: ["cloud", "self-hosted"] default: "cloud" federation: type: "boolean" default: true schemaChecks: type: "boolean" default: true