Architect Enterprise GraphQL Systems

This is a GraphQL architect skill focused on building scalable, performant, and secure GraphQL systems for enterprise applications, specializing in federation patterns, advanced optimization, and modern tooling. Federation and architecture coverage spans Apollo Federation v2 and subgraph design, GraphQL Fusion and composite schemas, schema composition and gateway configuration, and schema registry/governance. Schema design coverage spans schema-first development with SDL and code generation, interface/union types for flexible APIs, Relay specification compliance, and schema versioning strategies. Performance coverage centers on the DataLoader pattern for resolving N+1 problems, query complexity analysis and depth limiting, automatic persisted queries (APQ), and field/query-level response caching.

Use this skill when designing federated GraphQL architecture across teams, optimizing a schema to eliminate N+1 queries, implementing real-time subscriptions with proper authorization, migrating from REST to GraphQL, building a GraphQL gateway aggregating multiple microservices, or designing field-level caching and query-complexity limits for production safety. Security coverage spans field-level authorization, JWT integration, RBAC, query-cost analysis and rate limiting, and introspection hardening for production. Real-time coverage spans GraphQL subscriptions over WebSocket or SSE, live queries, and subscription filtering with authorization. It is not the right skill for tasks unrelated to GraphQL or REST-only API design with no GraphQL layer involved.

Input is a GraphQL architecture task - a new federated schema, a performance-degraded resolver, an auth/caching design, or a REST-to-GraphQL migration; output follows an eight-step response approach: analyze business requirements and data relationships, design a scalable schema with the appropriate type system, implement efficient resolvers with performance optimization, configure caching and security for production readiness, set up monitoring and analytics, design the federation strategy for distributed teams, implement testing and validation, and plan for schema evolution and backward compatibility. Tooling coverage spans Apollo Server/Federation/Studio, GraphQL Yoga, Pothos, Nexus, Prisma and TypeGraphQL, and Hasura/PostGraphile for database-first approaches.

Architects and backend teams building or scaling enterprise GraphQL systems - federated schemas, N+1-safe resolvers, production-grade security and caching - who want proven federation and optimization patterns applied consistently rather than designed from scratch per project. Enterprise integration coverage extends to REST-to-GraphQL migration strategies, legacy system data transformation, event sourcing and CQRS patterns behind a GraphQL layer, and API-gateway integration for hybrid REST/GraphQL approaches, with GraphQL mesh named for aggregating multiple upstream APIs into one schema. Its behavioral defaults: design schemas with long-term evolution in mind, prioritize developer experience and type safety, implement robust and meaningful error handling, and consider caching implications directly in schema design decisions rather than bolting caching on afterward.