AgentRules.org
RulesStacksClientsAuditorPrunerSelf-HealRFCsBenchmarkCLICI/CDAuthorsSubmit
This specification is maintained by the AgentRules Working Group. Have enhancements or want to claim maintainership?Submit Specification →
backendcritical PriorityID: graphql-apollo-dataloader

GraphQL Apollo Server & DataLoader Batching Standard

Guardrails for GraphQL APIs: mandatory DataLoader for nested field resolvers, query depth and complexity limits, and schema-first type safety.

Prohibited Anti-Pattern: AI writes nested GraphQL resolvers that fetch from DB inside each resolver, creating massive N+1 query explosions.

Export Ready-to-Drop Configuration

Select format below to copy code or download file directly.

---
description: GraphQL Apollo Server & DataLoader Batching Standard - Guardrails for GraphQL APIs: mandatory DataLoader for nested field resolvers, query depth and complexity limits, and schema-first type safety.
globs: **/*.graphql, **/*resolver*
alwaysApply: true
verified_by: "agentrules.org"
license: "CC-BY-4.0"
source: "https://agentrules.org/rules/graphql-apollo-dataloader"
---

# GraphQL Apollo Server & DataLoader Batching Standard

> **Severity**: CRITICAL | **Category**: backend
> **Anti-Pattern Warning**: AI writes nested GraphQL resolvers that fetch from DB inside each resolver, creating massive N+1 query explosions.

## System Constraints
You are a GraphQL API performance architect. Never fetch relational data directly inside nested resolvers without a DataLoader. Configure query complexity and depth limits to protect against denial-of-service query attacks.

## Strict Guidelines
- Wrap all relational resolver queries in DataLoader instances scoped per request context.
- Apply graphql-depth-limit (e.g. max depth 6) to prevent circular query attacks.
- Ensure all resolvers return structured domain errors rather than internal stack traces.

## Bad vs Good Implementations
### DataLoader Batching in Nested Resolvers

#### Bad Antipattern (AI Common Hallucination)
> **Why it fails**: Nested resolvers without DataLoader multiply database queries by the list length.
```typescript
// Anti-pattern: Direct database hit in nested resolver
const resolvers = {
  User: {
    posts: async (parent) => {
      // Fires 1 query for every single user returned in query!
      return db.posts.findMany({ where: { userId: parent.id } });
    }
  }
};
```

#### Production Standard (Correct)
> **Standard**: DataLoader combines all user IDs across the request tick and executes a single batched query.
```typescript
// Production Standard: Batched via DataLoader
const resolvers = {
  User: {
    posts: async (parent, _, context) => {
      // Batches all parent IDs into a single query: WHERE userId IN (...)
      return context.loaders.postsByUser.load(parent.id);
    }
  }
};
```
Recommended MCP Servers (mcp-serverlist.com)

Equip agent with system tools to verify code for this stack.

GraphQL AST MCP
Validate GraphQL schemas and analyze resolver complexity.
Recommended Agent Skills (askills.dev)

Ready-to-use executable skill functions tailored to this stack.

DataLoader Factory Builder
Generate type-safe request-scoped DataLoaders for GraphQL.
Architectural Specification & Invariant Rationale

Architectural Invariant Design: GraphQL Apollo Server & DataLoader Batching Standard

GraphQL Apollo Server & DataLoader Batching Standard defines an industrial-grade behavioral standard for backend engineering. Guardrails for GraphQL APIs: mandatory DataLoader for nested field resolvers, query depth and complexity limits, and schema-first type safety. Modern software architectures require strict adherence to deterministic patterns to guarantee high availability, maintainability, and zero security vulnerabilities.

Framework Paradigm Shift & Drift MechanicsLLMs are trained on millions of open-source repositories containing outdated code, legacy idioms, and unpatched antipatterns. When coding assistants generate implementations for this stack, they default to common statistical tokens: AI writes nested GraphQL resolvers that fetch from DB inside each resolver, creating massive N+1 query explosions. Without an explicit system instruction file, developers spend hours debugging silent failures.
Failure Modes & Production Blast Radius

Hazard Analysis: What Breaks Without This Rule

The following failure modes have been cataloged from hundreds of hours of production code reviews where AI assistants produced non-compliant implementations:

Failure ModeAI Symptom (The Anti-Pattern)SeverityProduction Impact & Remedy
AI Hallucination & Deprecation DriftAI writes nested GraphQL resolvers that fetch from DB inside each resolver, creating massive N+1 query explosions.Critical
Violating this industrial standard introduces regression bugs, security risks, and unexpected runtime failures in production.
Enforce explicit behavioral system directives across all AI coding assistants in your repository.
Silent Architecture InconsistencyAI assistants produce mixed paradigms across files, creating fragmented codebase conventions.Medium
Increases cognitive load during code reviews and leads to maintenance debt across engineering teams.
Pin project conventions in .cursor/rules, CLAUDE.md, and AGENTS.md so all team agents follow identical guardrails.
Architectural Directives in Detail

Step-by-Step Production Directives

Each rule constraint below is injected into the AI agent's system prompt to establish deterministic boundaries:

1

Wrap all relational resolver queries in DataLoader instances scoped per request context.

Wrap all relational resolver queries in DataLoader instances scoped per request context.

Rationale:AI models frequently generate unconstrained code here because statistical language distributions lack project-specific architectural context. Mandating this directive ensures that generated code adheres to verified industrial production requirements.
Enforcement:Integrated into the Agent Pack rule file. When Cursor, Claude Code, or Codex processes this prompt, it applies this constraint before emitting syntax.
2

Apply graphql-depth-limit (e.g. max depth 6) to prevent circular query attacks.

Apply graphql-depth-limit (e.g. max depth 6) to prevent circular query attacks.

Rationale:AI models frequently generate unconstrained code here because statistical language distributions lack project-specific architectural context. Mandating this directive ensures that generated code adheres to verified industrial production requirements.
Enforcement:Integrated into the Agent Pack rule file. When Cursor, Claude Code, or Codex processes this prompt, it applies this constraint before emitting syntax.
3

Ensure all resolvers return structured domain errors rather than internal stack traces.

Ensure all resolvers return structured domain errors rather than internal stack traces.

Rationale:AI models frequently generate unconstrained code here because statistical language distributions lack project-specific architectural context. Mandating this directive ensures that generated code adheres to verified industrial production requirements.
Enforcement:Integrated into the Agent Pack rule file. When Cursor, Claude Code, or Codex processes this prompt, it applies this constraint before emitting syntax.
Technical Questions & Answers

Frequently Asked Technical Questions

Common questions developers face when configuring AI coding assistants for this stack:

Q:Why is GraphQL Apollo Server & DataLoader Batching Standard critical for AI coding assistants?

Guardrails for GraphQL APIs: mandatory DataLoader for nested field resolvers, query depth and complexity limits, and schema-first type safety. Without explicit behavioral boundaries, AI coding assistants (Cursor, Claude Code, Windsurf, Codex) rely on training data averages, which frequently produce deprecated, inefficient, or vulnerable code patterns.

Q:How does adopting this rule prevent AI hallucinations?

This rule explicitly declares what the AI must avoid (AI writes nested GraphQL resolvers that fetch from DB inside each resolver, creating massive N+1 query explosions.) and prescribes verified positive examples. Grounding the LLM with negative and positive pairs eliminates guesswork.

Q:Which AI coding environments are supported?

This specification is multi-platform compatible: Cursor (.cursor/rules/*.mdc & .cursorrules), Anthropic Claude Code (CLAUDE.md), Windsurf (.windsurfrules), Codex / Cline (AGENTS.md), and GitHub Copilot (.github/copilot-instructions.md).

Q:Can I combine this rule with other technology stacks?

Yes. Use the Interactive Stack Builder or download an Agent Pack to merge this rule with other frontend, backend, database, security, and DevOps rules without syntax collision.

Open Specification · CC BY 4.0·Free for Personal, Team & Commercial In-Repo Use

Citation & Open Source Attribution Guidelines

This specification is licensed under Creative Commons Attribution 4.0 International (CC BY 4.0). You are completely free to adapt and share this rule in your workspace. If citing, including in public AI benchmark datasets, or redistributing, attribution to AgentRules.org is required.

Related BACKEND Rules

View all rules →
backend
42

Fastify 5 Schema Compilers & Encapsulation Production Standard

Fastify relies on lexical encapsulation contexts to sandbox decorators, hooks, and compiled validation/serialization schemas without memory leaks or cross-tenant bleed. In Fastify 5, misuse of global compilers or failing to encapsulate plugin boundaries causes compiled `fast-json-stringify` serializers and Ajv validators to either crash on duplicate IDs, leak private data across sibling scopes, or bypass JIT compilation optimizations. Production services must enforce strict encapsulation hierarchies and type-safe schema compilation across every routing subtree.

backend
68

Bun Embedded SQLite WAL Mode & Transaction Synchronization Standard

Production database standard for bun:sqlite. Mandates enabling Write-Ahead Logging (PRAGMA journal_mode = WAL), busy timeouts, and using db.transaction() for atomic operations without lock starvation.

backend
68

Drizzle ORM Batch API & Interactive Transaction Isolation Standard

Production database standard for Drizzle ORM (PostgreSQL & MySQL). Mandates using db.batch() over HTTP drivers to prevent round-trip waterfalls, explicit db.transaction() with serializable/read-committed isolation, and strictly avoids unawaited query promises.

1 Rule in Stack

GraphQL