Until GraphQL adds an official @export directive to the spec, implementers need to code this functionality through a custom directive.

Directives are among GraphQL’s most powerful features, but that’s only if the GraphQL server provides a good support for them.

You won’t read much about them in the countless blog posts about GraphQL scattered across the web, but directives are among the most powerful features of the popular query language.

Unlike REST, GraphQL supports both versioning and evolution as methods to handle breaking changes.

Principled GraphQL outlines an architectural strategy that enables teams to pluck resolvers in and out of the schema on an ad-hoc basis, making the schema dynamic.

We analyze and compare the two approaches to creating a GraphQL service: schema-first and code-first.

Using components to represent your GraphQL data structure on the server side is optimal for simplicity.

Of the many lessons learned from building a GraphQL server, conquering the N + 1 problem is among the most important.