←back to thread

How and why GraphQL will influence the Sourcehut alpha

(sourcehut.org)
153 points michaelanckaert | 1 comments | 11 Jun 20 04:46 UTC | HN request time: 0.236s | source
Show context
crabmusket ◴[11 Jun 20 13:03 UTC] No.23488357[source]▶
> Another (potential) advantage of GraphQL is the ability to compose many different APIs into a single, federated GraphQL schema.

If anyone else can share experiences of this sort of problems and solution, I'd be really interested to hear it. I've written non-GQL APIs before that back onto other internal and external services; what am I missing?

replies(2): >>23488403 #>>23491138 #
1. GordonS ◴[11 Jun 20 17:28 UTC] No.23491138[source]▶
I've mentioned my (negative) experience elsewhere in this thread. It wasn't actually me doing the implementation, but the result was a horrendous, unmaintainable and slow code base. Ultimately, no part of the team benefited from the use of GraphQL instead of REST.

To be fair, the same devs that built it using GraphQL would likely have made many of the same mistakes with a REST API, but I do feel it would at least have been easier to reason about the code.