![\"Ambiten\"](\"https://raw.githubusercontent.com/AmbitenHQ/ambiten/main/assets/ambiten-mark-192x192.png\")
\n
Fastify integration for the Ambiten runtime.\n
\n\nEstablish request-scoped execution boundaries, context propagation, multi-tenancy, and transaction-aware runtime behavior inside Fastify applications.
\n\n \n\n## Overview\n\n`@ambiten/adapter-fastify` connects Fastify applications to the Ambiten runtime.\n\nThe adapter establishes request execution boundaries using Fastify's lifecycle hooks so runtime context remains available throughout the lifecycle of each request. Tenant information, request metadata, transactions, logging, instrumentation, and runtime services can then participate consistently across handlers, plugins, services, and model operations.\n\nThe adapter does not replace Fastify. It allows Fastify to operate as an execution entry point for the Ambiten runtime.\n\n## Installation\n\n```text\nnpm install @ambiten/adapter-fastify\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-fastify\n```\n\n## Quick Start\n\n```text\nimport Fastify from \"fastify\";\nimport { AmbitenBootstrapFactory } from \"@ambiten/core\";\nimport { createFastifyAdapter } from \"@ambiten/adapter-fastify\";\n\nconst app = Fastify();\n\nconst adapter = createFastifyAdapter();\n\nconst bootstrap =\n await AmbitenBootstrapFactory.create({\n adapter\n });\n\nawait bootstrap.registerMultiTenancy(app);\n\nawait app.listen({\n port: 3000\n});\n```\n\nOnce installed, incoming requests automatically participate in the Ambiten execution model.\n\n## What the Adapter Provides\n\nThe adapter acts as the bridge between Fastify 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 downstream services and models.\n\nThis allows application code to remain focused on business logic while execution concerns remain coordinated by the runtime.\n\nRuntime Flow\n\n```text\nIncoming Request\n ↓\nFastify\n ↓\nAmbiten Adapter\n ↓\nAmbitenContext\n ↓\nModels & Services\n ↓\nMongoDB\n```\n\nThe adapter creates the execution boundary. The runtime then carries execution state throughout the remainder of the request lifecycle.\n\n## Fastify Integration\n\nThe adapter integrates directly with Fastify's request lifecycle and plugin system.\n\nRuntime context is established before application handlers execute and remains available throughout middleware, services, model operations, transactions, and asynchronous execution paths triggered by the request.\n\nThis ensures runtime state remains consistent while preserving Fastify's performance-oriented architecture.\n\n## Multi-Tenancy\n\nWhen multi-tenancy is enabled, tenant information can be resolved from incoming requests and made available throughout the active runtime context.\n\n```text\nRequest\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 through application layers.\n\n## Documentation\n\nComplete documentation is available at:\n\nhttps://docs.ambiten.dev\n\n- Related Packages\n- @ambiten/core\n- @ambiten/logger\n- @ambiten/create\n\n## License\n\nMIT\n","readmeFilename":"README.md"}![\"npm](\"https://img.shields.io/npm/v/@ambiten/adapter-fastify?style=flat-square\")
\n ![\"GitHub](\"https://img.shields.io/github/stars/AmbitenHQ/ambiten?style=flat-square&color=1E88E5\")
\n