![\"npm](\"https://img.shields.io/npm/v/@ambiten/adapter-express?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 Express integration for the Ambiten runtime.\n
\n\n\n Establish request-scoped execution boundaries, context propagation, multi-tenancy, and transaction-aware runtime behavior inside Express applications.\n
\n\n\n\n---\n\n## Overview\n\n`@ambiten/adapter-express` connects Express applications to the Ambiten runtime.\n\nThe adapter establishes request execution boundaries so runtime context remains available throughout the lifecycle of an incoming request. Tenant information, request metadata, transactions, logging, instrumentation, and runtime services can then participate consistently across controllers, services, middleware, and model operations.\n\nThe adapter does not replace Express. It allows Express to operate as an execution entry point for the Ambiten runtime.\n\n## Installation\n\n```bash\nnpm install @ambiten/adapter-express\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-express\n```\n\n## Quick Start\n\n```ts\nimport express from \"express\";\nimport { AmbitenBootstrapFactory } from \"@ambiten/core\";\nimport { createExpressAdapter } from \"@ambiten/adapter-express\";\n\nconst app = express();\n\nconst adapter = createExpressAdapter();\n\nconst bootstrap =\n await AmbitenBootstrapFactory.create({\n adapter\n });\n\nawait bootstrap.registerMultiTenancy(app);\n\napp.listen(3000);\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 Express 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\n## Runtime Flow\n\n```text\nIncoming Request\n ↓\nExpress\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## 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\n* `@ambiten/core`\n* `@ambiten/logger`\n* `@ambiten/create`\n\n## License\n\nMIT\n","readmeFilename":"README.md"}