Unified Repo — Appsync

Maintain a schema registry file or API catalog that lists deployed API endpoints, schema versions, and client compatibility.

Use directives to annotate fields with metadata (owner, deprecation, required-permissions).

Maintain a CHANGELOG for schema changes describing compatibility impact and migration steps.

An e‑commerce company with separate teams for User Profile, Inventory, and Orders each owns a folder in the unified repo. Their pipeline:

When the Orders team adds a new priority field to Order, only their folder and the composed API are re-deployed — but the change is atomic in the repo.

Tooling in the unified repo can enforce naming conventions, detect breaking changes (via graphql-inspector), and ensure that composed schemas are conflict-free before deployment. appsync unified repo

This document describes a recommended structure, conventions, and workflows for an "AppSync unified repo": a single repository that centralizes GraphQL schemas, resolvers, client-generated types, infrastructure-as-code, and developer tooling for projects using AWS AppSync (or an AppSync-compatible GraphQL service). It’s intended as a practical reference for teams aiming to improve consistency, speed of iteration, and cross-project reuse.

Consider a mid-sized e-commerce company with 12 microservices. Their old setup: Maintain a schema registry file or API catalog

A bug required changing a resolver to add a new field product.discount. The process took 5 days because:

After moving to a unified repo (using Turborepo and CDK): Use directives to annotate fields with metadata (owner,

Delivery time: 3 hours (90% reduction in lead time).

If you are building serverless applications on AWS, chances are you have fallen in love with AWS AppSync. It takes the heavy lifting out of GraphQL by handling real-time subscriptions, offline synchronization, and security.

But as your API grows—sprouting new resolvers, data sources, and schemas—a problem emerges: The Fragmented Pipeline.

You end up with CDK stacks pointing to S3 buckets with resolvers, Lambda functions buried in monorepo folders, and no single source of truth. Enter the AppSync Unified Repository.