So, what are the use cases for AppSync? For one, it's ideal for organizations that have multiple microservices, each with its own repository. By unifying these repositories under a single AppSync repository, organizations can simplify their development process, improve collaboration, and reduce bugs.
A unified repository requires a smart pipeline. You do not want to redeploy the entire GraphQL schema for a change to an unrelated Lambda data source. However, you do want atomicity. appsync unified repo
export interface IAppSyncRepository<T, TCreateInput, TUpdateInput> get(id: string): Promise<T>; list(limit?: number, nextToken?: string): Promise< items: T[]; nextToken?: string >; create(input: TCreateInput): Promise<T>; update(id: string, input: TUpdateInput): Promise<T>; delete(id: string): Promise<string>; subscribeToCreated(): Observable<T>; subscribeToUpdated(): Observable<T>; subscribeToDeleted(): Observable<string>; So, what are the use cases for AppSync