In AppSync, resolvers connect fields to data. If a resolver points to a Lambda (the most common pattern), that Lambda must exist in the AWS account before deployment. In fragmented repos, this creates a chicken-and-egg problem:
async query<T>(options: any): Promise<T> const result = await this.client.query<T>(options); return result.data;
| Challenge | Mitigation | | :--- | :--- | | | Split schema using #import or GraphQL modules. | | Cold start of many resolvers | Use Pipeline Resolvers to reuse functions. | | CDK deployment time | Use cdk watch for dev and lazy loading for resolvers. | | Local mocking of AppSync | Use AppSyncClient against a local Lambda + DynamoDB (via Docker). |