graphql-go VS apollo-server

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

Another interesting point is that executing fetches on the server can allow developers to more easily leverage caching. Next.js already handles caching out-of-the-box and I’m curious to see if the wider adoption of RSC reduces the need to combine React with solutions like Apollo Server and Apollo Client. While there are other benefits to these tools, RSC could provide similar caching behavior without the need to invest in a GraphQL solution.

There are several GraphQL server implementations, however, for this tutorial, we'll utilize Apollo GraphQL's Apollo Server, a lightweight and flexible JavaScript server that makes it easy to build GraphQL APIs.

As I mentioned, their main GraphQL server package is[1], so that's where the confusion came from. Thanks.

[1] https://github.com/apollographql/apollo-server/blob/9817bc47...

While working on this blog post, I learned that Apollo Server, the most popular GraphQL server for typescript, uses a similar method for adding error codes to GraphQL. It even lets you add custom errors. Hopefully, someday other GraphQL server projects will follow them. Until then, we’ve got a strong indication we took the right approach.

GraphQL is just a schema, there are many different implementations of a GraphQL server, AppSync being one of them. I mentioned Apollo server in this series as well.

After some head-scratching, I opened an issue on Apollo Server’s GitHub repository. There, Apollo Server contributor @​glasser shared a helpful suggestion: why not invoke our AuthPlugin from Apollo Server’s context function? Throwing from context would ensure we can control the HTTP status response without having to introduce more methods and error checks to our AuthPlugin (like unexpectedErrorProcessingRequest). With that suggestion in mind, we rewrote our AuthPlugin as follows:

Apollo as a middleware in Express.js, actually.

Apollo Server 3 Cookie Issue #5775

Lastly, instead of writing our API core ourselves, we'll be using the star of this episode --- Apollo Server (a.k.a. GraphQL server). It has detailed documentation available here.