2 ms·
You don't need to choose. You can do both. As graphQL let's you build extending other graphql api's, you could do one for each service, and a general one, this
by tough 5y ago
You don't need to choose. You can do both. As graphQL let's you build extending other graphql api's, you could do one for each service, and a general one, this should work nicely with you current setup I think.
Thegraph is mainly this for web3 stuff no?
- asim 5y agoOk interesting. Then I'll try to figure something out. I think we can probably find a way to handle all the graphql requests through a single endpoint. Thanks for the info.
- tough 5y agohttps://www.graphql-mesh.com/ https://www.graphql-mesh.com/ https://www.the-guild.dev/ https://www.the-guild.dev/ https://www.apollographql.com/docs/federation/ https://www.apollographql.com/docs/federation/