graphql-go VS express-graphql

And gqlgen is not alone in this. We found several more GraphQL frameworks that don’t take it upon themselves to address this problem. Widely used GraphQL server implementations, such as graphql-go/graphql and Python’s graphene, have the exact same gap of exposing messages of unexpected errors by default.

I have briefly looked into this and leaning towards GraphQL Go but don't yet know how it'll all come together. I'd prefer to stick with GraphQL if I can without it getting messy.

The tutorial uses the https://github.com/graphql-go/graphql

graphql-go. I use this to help me to implement the GraphQL.

I've done a bit of research and have found 99designs/gqlgen and graphql-go/graphql but I would like to hear from your experience.

Dude to readability and friendliness being my biggest concern, I decided to use https://github.com/graphql-go/graphql. First drawback I noticed is that you don’t have the option for a playground baked into your server. I’ve been using hoppscotch for testing my operations as a workaround. Only real struggle I faced was dealing with nullable arguments, but I grew to realize that it’s more of a feature

Best resource for learning stuff is the docs imo. The most popular library currently for graphql in Go is this one GitHub graphql-go/graphql.

For my current project we use ent (https://entgo.it) + gqlgen and its a really nice combo. As well as the two other popular graphql libraries for go (https://github.com/graphql-go/graphql and https://github.com/graph-gophers/graphql-go), I’ve also kept my eyes on graphjin (https://github.com/dosco/graphjin) and thunder (https://github.com/samsarahq/thunder) but to me there is no reason to not use ent with gqlgen - it’s just so nice :)

gqlgen is GraphQL server library. There are some graphql libraries for golang such as graphql-go/graphql. But I selected gqlgen becuase I really like a point of generating code after I defined schema.

A GraphQL server as an API Gateway for REST endpoints using graphql-go/graphql

It looked a little janky but it actually worked fine. But then I needed file uploads. Something graphql-zeus does not support. So I had to create a small wrapper for the SDK created so that it worked. And then also express-graphql, the server I was using, was deprecated.

This seems like a minor deal unless you're not using Express as your web framework. And an important note here is that Express GraphQL is being deprecated by the GraphQL Foundation. So if you're using Express for a GraphQL API, you should move away from it anyway.

You might have seen other GraphQL server solutions where the schema is implemented by using a more programmatic approach. Here is an example of how schemas are implemented using the express-graphql library. (link: https://github.com/graphql/express-graphql)

I'm not sure where the "8MB limit" comes from but, indeed, there are issues like this where, in some implementations, the response size is limited to 100KB: https://github.com/graphql/express-graphql/issues/346

With Node I used express-graphql as opposed to something like Apollo because it's lighter and less heavy on resources compared to Apollo.

Daniel Rearden listed the following reasons pushing him to create Helix, believing that these factors were absent from popular solutions like Apollo Server, express-graphql and Mercurius:

Express GraphQL is a library for building production ready GraphQL HTTP middleware. Despite the emphasis on Express in the repo name, you can create a GraphQL HTTP server with any HTTP web framework that supports connect styled middleware. This includes Connect itself, Express and Restify.

If you are using Node.js there are a lot of implementations of GraphQL servers with a few being express-graphql, apollo-server, mercurius, graphql-helix and more. And if you are using other languages, you can see a great list here

express-graphql GitHub Repository

Not sure about other libraries but it's certainly not the case for express-graphql on node.js. You can tie the graphql endpoint to any method you like. On the site I work on, we have a graphql endpoint that only accepts GET requests in production and is thus cacheable by Cloudfront. In dev and staging we accept all requests so that GraphIQL works.