![\"npm](\"https://img.shields.io/npm/v/@ambiten/adapter-graphql?style=flat-square\")
\n \n \n \n ![\"GitHub](\"https://img.shields.io/github/stars/AmbitenHQ/ambiten?style=flat-square&color=1E88E5\")
\n \n\n
\n GraphQL integration for the Ambiten runtime.\n
\n\n\n Establish context-aware execution boundaries for GraphQL queries, mutations, subscriptions, and resolver pipelines while preserving runtime continuity across the Ambiten ecosystem.\n
\n\n\n\n---\n\n## Overview\n\n`@ambiten/adapter-graphql` connects GraphQL execution to the Ambiten runtime.\n\nThe adapter establishes execution boundaries for queries, mutations, and subscriptions so runtime context remains available throughout resolver execution. Tenant information, request metadata, transactions, logging, instrumentation, and runtime services can then participate consistently across GraphQL operations.\n\nThe adapter does not replace GraphQL. It allows GraphQL execution to participate fully in the Ambiten runtime model.\n\n## Installation\n\n```bash\nnpm install @ambiten/adapter-graphql\n```\n\nIf you are starting a new application, installing the core runtime is also recommended:\n\n```bash\nnpm install @ambiten/core @ambiten/adapter-graphql\n```\n\n## Quick Start\n\n```ts\nimport {\n AmbitenBootstrapFactory\n} from \"@ambiten/core\";\n\nimport {\n createGraphQLAdapter\n} from \"@ambiten/adapter-graphql\";\n\nconst adapter = createGraphQLAdapter();\n\nconst bootstrap =\n await AmbitenBootstrapFactory.create({\n adapter\n });\n```\n\nOnce installed, GraphQL operations automatically participate in the Ambiten execution model.\n\n## What the Adapter Provides\n\nThe adapter acts as the bridge between GraphQL execution and the runtime.\n\nIt can establish request-scoped context, initialize tenant boundaries, propagate request metadata, participate in transaction-aware execution flows, and expose runtime state to resolvers, services, and models.\n\nThis allows resolver code to remain focused on business logic while execution concerns remain coordinated by the runtime.\n\n## Runtime Flow\n\n```text\nGraphQL Request\n ↓\nGraphQL Adapter\n ↓\nAmbitenContext\n ↓\nResolvers\n ↓\nModels & Services\n ↓\nMongoDB\n```\n\nThe adapter creates the execution boundary. The runtime then carries execution state throughout the remainder of the operation lifecycle.\n\n## Resolver Context\n\nGraphQL applications often require execution state to flow across multiple resolver layers.\n\nThe adapter automatically makes runtime context available throughout resolver execution so tenant information, request metadata, transactions, logging, and instrumentation remain consistent regardless of how deeply nested a resolver chain becomes.\n\n```text\nQuery\n ↓\nResolver\n ↓\nNested Resolver\n ↓\nService\n ↓\nModel\n```\n\nExecution context remains attached throughout the entire flow.\n\n## Multi-Tenancy\n\nWhen multi-tenancy is enabled, tenant information can be resolved during GraphQL execution and made available throughout the active runtime context.\n\n```text\nGraphQL Request\n ↓\nTenant Resolution\n ↓\nAmbitenContext\n ↓\nTenant-Aware Execution\n```\n\nThis allows models and services to operate against the correct tenant boundary without manually passing tenant identifiers between resolvers.\n\n## Subscriptions\n\nThe adapter also supports runtime-aware subscription execution.\n\nSubscription events can participate in the same execution model used by queries and mutations, allowing tenant information, instrumentation, logging, and runtime metadata to remain consistent across real-time GraphQL workflows.\n\n## Documentation\n\nComplete documentation is available at:\n\nhttps://docs.ambiten.dev\n\n## Related Packages\n\n* `@ambiten/core`\n* `@ambiten/logger`\n* `@ambiten/create`\n\n## License\n\nMIT\n","readmeFilename":"README.md"}