by jens-neuse
Good GraphQL schemas start from client needs, not backend models. Ten principles—from capability-based design to organizational alignment—establish patterns for maintainable, evolvable APIs.
by steven-chambers
At Netflix's scale of 160 million resolver executions per second, even innocuous framework code can become a critical bottleneck. Doubling fleet efficiency came from fixing a simple introspection API call.
Patterns and tools for building GraphQL APIs—from schema design to Meta's fragment philosophy
by productdevbook
A Nitro module that adds GraphQL servers with automatic schema discovery, type generation, and zero-config defaults. Supports GraphQL Yoga and Apollo Server.
by matt-mahoney
Meta's @async directive solves the problem of paying server compute costs for data that may never be displayed, using a persist-time transform that defers fragments until explicitly requested.
by benjie-gillam
GraphQL's error propagation destroys sibling data when non-null fields fail. A 512-byte library called graphql-toe transforms error-nulls into thrown errors, letting schemas express business semantics instead of error boundaries.
by janette-cheng
GraphQL fragments describe data requirements for components, not reduce code duplication. Reusing fragments causes overfetching. Use fragment models, collocate GraphQL with code, and write GraphQL that mirrors your component structure.
by samer-buna
A practical guide to building and consuming GraphQL APIs, covering schema design, resolvers, database integration, and client-side usage with Apollo.