graphjin VS graphql-go

This one looks interesting if you like GraphQL… https://graphjin.com

You're right. Django made a ton of tables, and it's pretty insightful to think about all the stuff it's trying to consider and a nightmare to migrate that framework. Django might have simplified some stuff, but it's still too opaque for my taste and the overall end goals of the project. Currently, I'm testing using graphjin (it doesn't have the best documentation, but it does boast an SQL generation capability that I philosophically think is the best way to do things).

Checkout GraphJin it's an automatic GraphQL to SQL compiler, you write your database queries in GraphQL instead of SQL and it compiles them into efficient SQL on the fly. Works as a library in GO and NodeJS. https://github.com/dosco/graphjin

In GraphJin an automatic GraphQL to SQL compiler we use the gnomock library it startups a database instance (docker) then create the schema and tests data and finally our code connects to it and runs a series of tests. We run these across Mysql, Postgres and a few other DB's. Gnomock supports a wide range of them. Right now we don't take down the db for every test only between test runs but its fast enough that we could. This whole thing runs of a simple `go test -v .` command and we run it on every commit using a githook. https://github.com/dosco/graphjin/blob/master/tests/dbint_te...

This was a bug in GraphJin it has since been fixed. The issue was that you were trying to have multiple subscriptions over a single websocket this did not work (it should) and now it does. https://github.com/dosco/graphjin/commit/43e619b2ff392dd42b99a4d56074a041a54b0e1c

Not exactly GraphQL is just a format to define what data you want back from someplace. You can use it in a browser app to request data from a backend GraphQL server or you can use it as an ORM within your backend app to fetch data from a database using a library like GraphJin. https://github.com/dosco/graphjin

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