Recomended way to split graphql API in different microservices about serverless-graphql

[nikgraf]

You could create multiple GraphQL endpoint, but I wouldn't recommend it. Internally we actually have one Lambda to handle the GraphQL queries which in the resolve functions calls other Lambdas (which we structured as microservices). Yes, this is a bit more expensive and adds a small overhead in terms of performance, but we decided to go that route to increase developer productivity and have clear separation.

Doing everything in one handler will work as well, but then I recommend to think about how to structure you code early on.

[morgs32]

@nikgraf have an example? I'm wondering how you break out the query and ship it to another graphql server

[nikgraf]

@morgs32 sorry. Missed that. Unfortunately I don't have anything I can share with you 🙁

[sid88in]

@nikgraf @morgs32 for multiple graphql endpoints you might wana to look at Schema Stitching : https://dev-blog.apollodata.com/graphql-schema-stitching-8af23354ac37

[nikgraf]

Totally!