GraphQL Yoga

Understanding yoga helps you work with GraphQL confidently. Here you will learn the core ideas behind yoga, see working code, and pick up best practices used on real teams.

Yoga Overview

Yoga is a building block you will reach for often in GraphQL. It keeps related logic together and makes your intent obvious to reviewers and future maintainers.

When you learn yoga properly, you avoid the guesswork that leads to bugs and rework. The example below shows the shape you will use in most real GraphQL projects.

import { createYoga, createSchema } from 'graphql-yoga';
import { createServer } from 'node:http';

const yoga = createYoga({
  schema: createSchema({ typeDefs, resolvers }),
});
createServer(yoga).listen(4000);

GraphQL Yoga is a batteries-included server that runs the same schema and resolvers.

Yoga Example

const typeDefs = gql`
  type Query { hello: String! }
`;
const resolvers = { Query: { hello: () => 'world' } };
const server = new ApolloServer({ typeDefs, resolvers });

Start from a minimal Yoga example and grow it only as needed.
Keep configuration explicit so Yoga behaves the same in every environment.
Name things clearly so teammates understand your Yoga at a glance.
Add tests around Yoga early to lock in expected behaviour.

GraphQL Cheatsheet

Quick GraphQL reference related to yoga.

Concept	Example	Purpose
Schema	`type Query { user(id: ID!): User }`	Define the API shape
Resolver	`Query: { user: (_, { id }) => ... }`	Provide field data
Query	`query { user(id: 1) { name } }`	Read exactly what you need
Mutation	`mutation { createUser(input) { id } }`	Change data
Subscription	`subscription { postAdded { id } }`	Real-time updates
Context	`context: ({ req }) => ({ user })`	Auth and shared state
DataLoader	`loader.load(id)`	Batch to avoid N+1

How Yoga Works in GraphQL

Yoga fits into GraphQL's model of a single typed schema that clients query for exactly the data they need. The server resolves each requested field through resolver functions.

GraphQL Yoga is a batteries-included server that runs the same schema and resolvers.

The schema is the contract between client and server.
Resolvers fetch data field by field, including nested types.
Clients request only the fields they use, avoiding over-fetching.
Context carries auth and shared services into every resolver.

Practical Guidance for Yoga

In production, yoga should be efficient and secure. Batch data access with DataLoader, guard resolvers with authorization, and limit query depth and complexity.

Concern	Recommendation
N+1 queries	Batch with DataLoader
Security	Auth in context, depth/complexity limits
Errors	Typed GraphQLError with extension codes
Performance	Cache and paginate large lists

Common Mistakes

Skipping error handling and edge cases when wiring up yoga.
Leaving yoga untested, so regressions slip into production.
Over-engineering yoga before you actually need the extra flexibility.
Ignoring documentation, which makes yoga hard for the next developer to change.

Key Takeaways

Yoga is a core part of working effectively with GraphQL.
Start small and keep yoga focused on a single responsibility.
Apply consistent patterns so yoga scales across your project.
Test and document yoga to keep it maintainable over time.

Pro Tip

Pair yoga with automated tests from day one. It is far cheaper to catch GraphQL regressions in CI than in production.