GraphQL Schema

A GraphQL schema is a public contract that clients build against for years, and a resolver layer is an open invitation for N+1 queries and abusive nesting. This skill designs schemas clients love and servers survive: model the domain rather than the database, batch every relationship resolver, and put hard limits on what a single query may cost - because removing a shipped field or fixing a hot N+1 under load is 10x the effort of designing it right.

Operating procedure

Step 1: Gather inputs

• The domain nouns and the operations clients actually need (screens/use-cases, not tables).
• Largest list sizes and expected query shapes; who the clients are (first-party only vs public API - public means stricter limits).
• Data sources behind each type and which relationships cross a database or service boundary.
• Single graph or federated subgraphs.

Step 2: Model the graph