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년 전

로그인하지 않았습니다. 로그인해야 답변을 게시할 수 있습니다.

좋은 답변은 질문에 명확하게 답하고 건설적인 피드백을 제공하며 질문자의 전문적인 성장을 장려합니다.

질문 답변하기에 대한 가이드라인

관련 콘텐츠