←back to thread

How and why GraphQL will influence the Sourcehut alpha

(sourcehut.org)
153 points michaelanckaert | 2 comments | 11 Jun 20 04:46 UTC | HN request time: 0.618s | 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. maddyboo ◴[11 Jun 20 13:09 UTC] No.23488403[source]▶
I think Drew is referring to composition in terms of API end-user code, not sr.ht code, e.g. making it possible for the user write a single GQL query that combines data from multiple sr.ht services.
replies(1): >>23495197 #
2. crabmusket ◴[12 Jun 20 01:52 UTC] No.23495197[source]▶
Ah, I think that makes a little more sense. Thanks!