Skip to content
Switch branches/tags

Latest commit


Git stats


Failed to load latest commit information.
Latest commit message
Commit time

@zombiezen's GraphQL Go Server


This repository contains Go packages for creating a GraphQL server. The primary focus is on simplicity and efficiency of the server endpoints.

This library is pre-1.0, so there may still be API changes. You can find known issues about compliance to the specification or production-readiness in the issue tracker.

Getting Started

The easiest way to get started with this library is to follow the directions in the graphql-go-app README to create a project. This will set you up with a GraphQL server with a Single-Page Application using TypeScript and React.

If you want to integrate the library into an existing project, then run:

go get

Then, look at the main package example for how to write a server type and the graphqlhttp package example for how to start serving over HTTP.

Comparison With Other Libraries

A quick look at the official GraphQL libraries for Go may leave you wondering, "why another server library?" Simply, @zombiezen hit roadblocks to writing apps with other libraries and wanted to try a different API approach.

This library intentionally focuses on: follows the graphql-js reference implementation, basically replicating its API verbatim. Unfortunately, this leads to a fairly verbose approach to defining the server's schema in code rather than the GraphQL IDL. Further, while you can do limited look-ahead of output selection sets via ResolveInfo, this only returns the ASTs and requires the caller to interpret the fragments themselves (graphql-go/graphql#157). The library also doesn't provide any out-of-the-box utilities for serving over HTTP.

@zombiezen very much liked the approach that took toward the problem: it uses the IDL and the Go type system rather than a large package-specific data structure. This results in a small ramp-up time and application code that is fairly straightforward to follow.

However, the library has a few issues. It does not support look-ahead at all (graph-gophers/graphql-go#17). The API conflates schema parsing with server object binding (i.e. graphql.ParseSchema takes a resolver), so many servers end up passing dependencies through the Context. The library makes it difficult to test servers that use it, since its responses are always JSON-formatted, which makes it hard to compare specific fields. While JSON is a common serialization format used with GraphQL, the spec permits any serialization.

gqlgen is another common GraphQL solution for Go. Its primary selling point is that rather than using reflection, it generates Go code based on a GraphQL schema and a YAML configuration file.

While this seems productive and helpful, @zombiezen has a great deal of experience with code generators and knows their strengths and limitations. Notably, code generators are difficult to reason about when generated code is mixed with user-written code. Names can conflict and special configuration directives are required. gqlgen is no exception, and while gqlgen may be productive for smaller projects, code generation provides unacceptable complexity for larger projects.

Of all the other Go libraries for GraphQL @zombiezen has surveyed, gqlgen is definitely the most feature-complete, but @zombiezen found these features hard to use or find due to the large API surface area dedicated to supporting the generated code. Further, critical features like examining the selection set are limited to a single level of depth, whereas this library permits checking arbitrary depth.

In practice, the code someone would write for this library is largely similar to gqlgen, but with far less glue and build complexity. By performing up-front type structure checks, this library is able to get many of the same guarantees without nearly as much intrusion on Go developer workflow.


Apache 2.0


GraphQL server package for Go with a focus on simplicity and efficiency




Code of conduct




Sponsor this project



No packages published