graphql▌

GraphQL schema design, federation architecture, and real-time subscription implementation for distributed graph systems. \n \n Covers schema-first design with Apollo Federation 2.5+, including entity resolution, subgraph composition, and federation directives \n Provides resolver patterns with DataLoader for N+1 prevention, batching, and caching across distributed architectures \n Includes query complexity analysis, depth limiting, and field-level security to prevent abuse before deployment \n S

Implement GraphQL APIs with proper schema design, resolver patterns, error handling, and performance optimization for flexible client-server communication.

You are an expert GraphQL architect specializing in enterprise-scale schema design, federation, performance optimization, and modern GraphQL development patterns.

You're a developer who has built GraphQL APIs at scale. You've seen the N+1 query problem bring down production servers. You've watched clients craft deeply nested queries that took minutes to resolve. You know that GraphQL's power is also its danger.

GraphQL schema design, resolver patterns, and production safety best practices. \n \n Covers nine core capabilities including schema design, resolvers, federation, subscriptions, DataLoader, code generation, and Apollo tooling for both server and client \n Emphasizes critical production hazards: N+1 query problems, unlimited query depth leading to DoS, introspection exposure, and improper authorization scoping \n Provides patterns for type-safe schemas with intentional nullability, batch query o

Best practices guide for writing efficient, type-safe GraphQL operations and organizing them with fragments. \n \n Covers queries, mutations, subscriptions, and fragments with naming conventions, variable syntax, and directive usage \n Emphasizes core principles: request only needed fields, name all operations, use variables instead of hardcoded values, and include id fields for cacheability \n Recommends colocating fragments with components and using @include / @skip directives for conditional

Industry best practices guide for designing intuitive, performant, and maintainable GraphQL schemas. \n \n Covers core design principles including client-centric type organization, explicit nullability patterns, and backwards-compatible evolution strategies \n Provides reference documentation on types, naming conventions, cursor-based pagination, error modeling, and security considerations \n Includes practical patterns for interfaces, unions, input types, mutations, and ID strategies with code