- Newest
- Most votes
- Most comments
Having the same problem regarding AppSync.
+1
Edited by: svenm on Jul 4, 2019 4:16 AM
Hi,
Schema stitching is a request we've heard from many customers, and I can take this as a +1 to prioritizing that in a future release.
In the meantime, have you checked out the Amplify CLI? It can help manage source control and collaboration on larger schemas.
Thanks,
Jeff
Thanks for the +1, Jeff.
We have done more in-depth researches on AppSync.
Amplify CLI, to be honest, does not help in splitting large schemes into manageable chunks. We need to organize our schemas by business domains, which is in turn managed by individual teams.
I want to add that schema stitching only makes sense when worked with type extension, such feature first appeared in the April 2016 release of the GraphQL specs. We really need these available to move on from our server caps in EC2.
The serverless framework's AppSync plugin https://github.com/sid88in/serverless-appsync-plugin has now support to stich multiple schema files thanks to one of my coworkers. It got merged with MR https://github.com/sid88in/serverless-appsync-plugin/pull/227.
The underlying package merge-graphql-schemas is what we've been using in the Apollo Server source codes. Although we have already invented way to automatically map resolver templates, this PR really helps users in the future, really appreciate it.
Relevant content
- asked 2 months ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 2 years ago