search

tengen-io / server

:white_circle: Server implementation of the board game Go
MIT License
13 stars 4 forks source link

Evaluate different GraphQL implementations #47

Open eaceaser opened 5 years ago

eaceaser commented 5 years ago

So, I'm really not a fan of the fact that the current GQL library we're using is not type safe. Also it hasn't seen much development for a while, which is a bit concerning given that GQL is a relatively new protocol. Also according to some old benchmarks, the library we're using is slower than the alternatives by an order of magnitude. We should confirm that result.

This uses code generation, so there will be an additional build step to generate the code. However, it generates typesafe code. I'm not the world's biggest fan of code generation, but this is golang and that pattern is used in various places.

Parses a schema file, which I kinda like. Has type-safe arguments.

eaceaser commented 5 years ago

https://medium.freecodecamp.org/deep-dive-into-graphql-with-golang-d3e02a429ac3

this is timely

eaceaser commented 5 years ago

I'm working on a large model and API refactor; I'm trialing out gqlgen at the same time. Check https://github.com/tengen-io/server/tree/gql_next