4 ms·
My first instinct is definitely together, but perhaps namespaced, which will lead to some redundant naming but makes sure there are no conflicts. As a consumer
by RedShift1 4y ago
My first instinct is definitely together, but perhaps namespaced, which will lead to some redundant naming but makes sure there are no conflicts. As a consumer you don't want to run to different endpoints all the time to get different things done, you want one endpoint and change the operation through the GraphQL query/mutation/subscription.
- asim 4y agoI thought this might be the case. Hence needing to do something federated. But initially we might be able to group all the schemas into one giant graphql server. I don't have enough experience with graphql personally so will probably need some help with this.
- ricopags 4y agoYou might consider checking out www.onegraph.com and www.stepzen.com if you do go the GraphQL route [OneGraph as competition, StepZen as perhaps a solution]