Recommendations in managing large schemas

0

Our team is working with ~30 domains written in Apollo Server, and we are hitting bottlenecks of autoscaling with EC2.

We are looking for possibilities in migrating to either AppSync or Lambda, they both comes short in different ways.

Lambda + API Gateway: We can theoretically bundle the whole thing into lambda, but subscriptions are inherently impossible by the nature of how Lambda is designed.

AppSync: It is missing ways to manage large schemas. Unfortunately, with our Apollo background, we can only approach the problem with their ways. We can do schema stitching ourselves before deployment, but the lack of type extension support really hits us like a rock.

I could really use some help on ways to manage large schemas.

iLake
已提問 5 年前檢視次數 625 次
5 個答案
0

Having the same problem regarding AppSync.

+1

Edited by: svenm on Jul 4, 2019 4:16 AM

svenm
已回答 5 年前
0

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

已回答 5 年前
0

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.

iLake
已回答 5 年前
0

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.

已回答 5 年前
0

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.

iLake
已回答 5 年前

您尚未登入。 登入 去張貼答案。

一個好的回答可以清楚地回答問題並提供建設性的意見回饋,同時有助於提問者的專業成長。

回答問題指南