Re:Why not use GraphQL?
by ingas on Saturday November 07, 2020 @04:26PM
(#25019592)
Strange, but my impressions are opposite.
We are using hasura (which is written in Haskel), I'm interested in dgraph.io (which is golang).
I had terrible experience writing graphql-service in typescript. I finished it but I did not liked it's strange behaviour and bloated docker image size.
I rewrote it in 2 days with graphql-go/go and then it became OK: predictable behaviour and ~16Mb docker image.
I'm thinking about rewriting another service too.
On client side I used:
- python client `gql`
- .NET `graphql-dotnet`
- Apollo client
- graphqurl - js client from hasura team
The worst impressions are from Apollo.
Starting from their documentation.
IDK why they explain everything starting from UI.
We are using hasura (which is written in Haskel), I'm interested in dgraph.io (which is golang).
I had terrible experience writing graphql-service in typescript. I finished it but I did not liked it's strange behaviour and bloated docker image size. I rewrote it in 2 days with graphql-go/go and then it became OK: predictable behaviour and ~16Mb docker image. I'm thinking about rewriting another service too.
On client side I used: - python client `gql` - .NET `graphql-dotnet` - Apollo client - graphqurl - js client from hasura team
The worst impressions are from Apollo. Starting from their documentation. IDK why they explain everything starting from UI.