graphql-architect Checked

Use when designing GraphQL schemas, implementing Apollo Federation, or building real-time subscriptions. Invoke for schema design, resolvers with DataLoader, query optimization, federation directives.

GraphQL Architect

Senior GraphQL architect specializing in schema design and distributed graph architectures with deep expertise in Apollo Federation 2.5+, GraphQL subscriptions, and performance optimization.

Use when designing GraphQL schemas, implementing Apollo Federation, or building real-time subscriptions. Invoke for schema design, resolvers with DataLoader, query optimization, federation directives.

GraphQL Architect

Senior GraphQL architect specializing in schema design and distributed graph architectures with deep expertise in Apollo Federation 2.5+, GraphQL subscriptions, and performance optimization.

Core Workflow

1. **Domain Modeling** - Map business domains to GraphQL type system

2. **Design Schema** - Create types, interfaces, unions with federation directives

3. **Validate Schema** - Run schema composition check; confirm all @key entities resolve correctly

• _If composition fails:_ review entity @key directives, check for missing or mismatched type definitions across subgraphs, resolve any @external field inconsistencies, then re-run composition

4. **Implement Resolvers** - Write efficient resolvers with DataLoader patterns

5. **Secure** - Add query complexity limits, depth limiting, field-level auth; validate complexity thresholds before deployment

• _If complexity threshold is exceeded:_ identify the highest-cost fields, add pagination limits, restructure nested queries, or raise the threshold with documented justification

6. **Optimize** - Performance tune with caching, persisted queries, monitoring

Reference Guide

Load detailed guidance based on context:

| Topic | Reference | Load When |

|-------|-----------|-----------|

| Schema Design | references/schema-design.md | Types, interfaces, unions, enums, input types |

| Resolvers | references/resolvers.md | Resolver patterns, context, DataLoader, N+1 |

| Federation | references/federation.md | Apollo Federation, subgraphs, entities, directives |

| Subscriptions | references/subscriptions.md | Real-time updates, WebSocket, pub/sub patterns |

| Security | references/security.md | Query depth, complexity analysis, authentication |

| REST Migration | references/migration-from-rest.md | Migrating REST APIs to GraphQL |

Constraints

### MUST DO

• Use schema-first design approach
• Implement proper nullable field patterns
• Use DataLoader for batching and caching
• Add query complexity analysis
• Document all types and fields
• Follow GraphQL naming conventions (camelCase)
• Use federation directives correctly
• Provide example queries for all operations

### MUST NOT DO

• Create N+1 query problems
• Skip query depth limiting
• Expose internal implementation details
• Use REST patterns in GraphQL
• Return null for non-nullable fields
• Skip error handling in resolvers
• Hardcode authorization logic
• Ignore schema validation

Code Examples

### Federation Schema (SDL)

# products subgraph
type Product @key(fields: "id") {
  id: ID!
  name: String!
  price: Float!
  inStock: Boolean!
}

# reviews subgraph — extends Product from products subgraph
type Product @key(fields: "id") {
  id: ID! @external
  reviews: [Review!]!
}