: Run cdk diff or serverless deploy --dry to review exactly what infrastructure changes will occur.
my-appsync-repo/ ├── backend/ │ ├── schema/ │ │ └── schema.graphql │ ├── resolvers/ │ │ ├── Query/ │ │ │ ├── getItem.js │ │ │ └── listItems.js │ │ ├── Mutation/ │ │ │ ├── createItem.js │ │ │ └── updateItem.js │ │ └── pipelines/ │ ├── datasources/ │ │ └── datasources.json │ └── functions/ │ └── auth.js ├── infrastructure/ │ ├── appsync-stack.ts (CDK) │ └── config/ ├── tests/ │ ├── unit/ │ └── integration/ ├── scripts/ │ └── deploy.sh └── README.md appsync repo
This is where the business logic resides. In this repository structure, resolvers are categorized by data source: : Run cdk diff or serverless deploy --dry
The is a highly efficient software architecture design pattern used to decouple your GraphQL resolvers from the underlying data sources, such as Amazon DynamoDB, AWS Lambda, or Amazon Aurora. A scalable AppSync repository separates the GraphQL schema,
A scalable AppSync repository separates the GraphQL schema, business logic (resolvers), testing suites, and deployment configurations. Here is a proven monorepo-friendly structure using AWS CDK and JavaScript/TypeScript resolvers: