Explore WunderGraph vocabulary — virtual graph federation, namespace collision avoidance, TypeScript operations, and live queries.
0 / 5 completed
1 / 5
During standup, an API platform engineer explains the WunderGraph virtual graph. What is it?
WunderGraph's virtual graph is a merged schema generated at build time from all configured data sources. Unlike Apollo Federation (which requires subgraphs to implement the Federation spec), WunderGraph can federate any GraphQL API, REST endpoint, database, or gRPC service — presenting a unified GraphQL surface to clients.
2 / 5
In a PR review, a colleague adds an API namespace to a WunderGraph data source config. What does it prevent?
Namespacing in WunderGraph prefixes every type and field from a data source. If both your GitHub and GitLab integrations expose a User type, namespacing them as github_User and gitlab_User prevents collisions in the merged virtual graph. Queries use the prefixed names: { github_user { login } }.
3 / 5
An incident reveals that data source connector configuration is stale after an upstream API change. How do connectors work?
WunderGraph connectors introspect data sources at wundergraph generate time — not at runtime. This means generated TypeScript types are always in sync at build time. When an upstream API adds or removes fields, re-running wundergraph generate regenerates the types and surfaces breaking changes as TypeScript compile errors.
4 / 5
In a design review, the team evaluates TypeScript operations in WunderGraph. What do they enable?
TypeScript operations live in .wundergraph/operations/ and are compiled by WunderGraph into optimised API endpoints. They have full access to the virtual graph's data sources via the internal client, TypeScript for business logic, and return typed responses. This eliminates the need for a separate custom backend for data aggregation or transformation.
5 / 5
During a code review, a teammate adds @live to a WunderGraph operation. What does this enable?
@live queries in WunderGraph add real-time behaviour to any existing query operation. WunderGraph polls the upstream source at a configurable interval (or on webhook trigger) and pushes diffs to clients over Server-Sent Events — a simpler infrastructure requirement than WebSockets. No upstream subscription support is needed.