database
规范 NestJS 应用的数据访问层设计,涵盖 ORM 选型、连接池与分片等可扩展架构,强制使用仓库模式隔离数据库逻辑,通过异步配置加载敏感信息,禁用生产环境自动同步,依赖迁移脚本实现零停机演进,并统一要求分页、索引声明与事务保护。
数据与分析数据库软件开发
| name | NestJS Database |
| description | Data access patterns, Scaling, Migrations, and ORM selection. |
| metadata | {"labels":["nestjs","database","typeorm","prisma","mongodb"],"triggers":{"files":["**/*.entity.ts","prisma/schema.prisma"],"keywords":["TypeOrmModule","PrismaService","MongooseModule","Repository"]}} |
NestJS Database Standards
Priority: P0 (FOUNDATIONAL)
Database integration patterns and ORM standards for NestJS applications.
Selection Strategy
See references/persistence_strategy.md for database selection matrix and scaling patterns (Connection Pooling, Sharding).
Patterns
- Repository Pattern: Isolate database logic.
- TypeORM: Inject
@InjectRepository(Entity). - Prisma: Create a comprehensive
PrismaService.
- TypeORM: Inject
- Abstraction: Services should call Repositories, not raw SQL queries.
Configuration (TypeORM)
- Async Loading: Always use
TypeOrmModule.forRootAsyncto load secrets fromConfigService. - Sync: Set
synchronize: falsein production; use migrations instead.
Migrations
- Never use
synchronize: truein production. - Execution: Run via init container or CD step.
- Zero-Downtime: Use Expand-Contract pattern (Add -> Backfill -> Drop).
- Seeding: Use factories for dev data; only static dicts for prod.
Best Practices
- Pagination: Mandatory. Use limit/offset or cursor-based pagination.
- Indexing: Define indexes in code (decorators/schema) for frequently filtered columns (
where,order by). - Transactions: Use
QueryRunner(TypeORM) or$transaction(Prisma) for all multi-step mutations to ensure atomicity.
数据与分析
数据库
软件开发









