How and why GraphQL will influence the Sourcehut alpha

Re:How and why GraphQL will influence the Sourcehut alpha by dmitriid on Thursday June 11, 2020 @07:22AM (#23487619)

We're exploring a GraphQL serv(er/ice) for an internal back office system. It needs to combine multiple APIs into a single GraphQL interface. And everything just breaks apart :) (we have PoCs in C# and Java for now).

[ Parent | on HN ]

Re:How and why GraphQL will influence the Sourcehut alpha by gavinray on Thursday June 11, 2020 @09:49AM (#23488835)

You can use Remote Schemas in Hasura to combine multiple API's, and Remote Joins to join relational data across data sources:

https://hasura.io/docs/1.0/graphql/manual/remote-schemas/ind...

https://hasura.io/blog/remote-joins-a-graphql-api-to-join-da...

If you need to convert your API's into a GraphQL first, you can wrap the endpoints with resolvers yourself, or use automated tooling:

https://github.com/Urigo/graphql-mesh

https://github.com/IBM/openapi-to-graphql

[ Parent | on HN ]

Re:How and why GraphQL will influence the Sourcehut alpha by dmitriid on Friday June 12, 2020 @02:23AM (#23496579)

I took a quick peek, it's no different than writing your own resolvers in any other implementation.

[ Parent | on HN ]