SYSTEM Cited by 1 source
Netflix Enterprise GraphQL Gateway¶
Netflix's Enterprise GraphQL Gateway is the federated GraphQL entry point for Netflix's internal applications — the "single graph" the rest of Netflix's internal tooling queries against (Source: sources/2025-06-14-netflix-model-once-represent-everywhere-uda).
The gateway uses GraphQL Federation to stitch together type resolvers contributed by many Domain Graph Services (DGSs) — Netflix's open-sourced Spring-Boot-based GraphQL framework. Each DGS owns a subset of the federated schema; the gateway composes them into one queryable graph.
Role inside UDA¶
Two UDA-adjacent roles are named in the source post:
- Upper's own API is federated in. "Upper itself is projected into a generated Jena-based Java API and GraphQL schema used in GraphQL service federated into Netflix's Enterprise GraphQL gateway." The metamodel's introspection surface is part of the gateway.
- PDM-generated GraphQL schemas land here. "These taxonomy models are projected into Avro and GraphQL schemas, automatically provisioning data products in the Warehouse and GraphQL APIs in the Enterprise Gateway." Reference-data domain models auto-provision gateway endpoints.
The gateway is, in other words, one of UDA's main data-container representation targets — a platform UDA projects schemas into.
Status on the wiki¶
Stub page — flagged for expansion when Netflix's dedicated GraphQL-federation posts are ingested ("How Netflix Scales Its API with GraphQL Federation — Part 1", etc.).
Seen in¶
- sources/2025-06-14-netflix-model-once-represent-everywhere-uda — Upper + PDM both project GraphQL schemas into the gateway.
Related¶
- systems/netflix-domain-graph-service — the DGS framework that hosts federated subgraphs.
- systems/netflix-uda · systems/netflix-upper · systems/netflix-pdm — UDA components that emit into the gateway.
- companies/netflix — Tier-1 source.