Pêkên nawa database (TypeORM/Prisma) karo NestJS?

Question

Accepted Answer

NestJS nggabung kanthi rapi karo database via ORMs — sing paling umum **TypeORM** (integrasi official `@nestjs/typeorm`) lan **Prisma** (ORM modern, type-safe sing digunakake via custom service). Loro-lorone cocok karo struktur module/provider/DI ing NestJS. ## Integrasi TypeORM ```ts // 1. configure the connection in a module @Module({ imports: [ TypeOrmModule.forRoot({ type: "postgres", url: process.env.DATABASE_URL, entities: [User], synchronize: false, // ⚠️ NEVER true in production (use migrations) }), TypeOrmModule.forFeature([User]), // register entities for this feature module ], }) export class UsersModule {} ``` ```ts // 2. define an entity (maps to a table) @Entity() export class User { @PrimaryGeneratedColumn() id: number; @Column() name: string; @Column({ unique: true }) email: string; } ``` ```ts // 3. inject the repository into a service @Injectable() export class UsersService { constructor( @InjectRepository(User) private usersRepo: Repository, ) {} findAll() { return this.usersRepo.find(); } findOne(id: number) { return this.usersRepo.findOneBy({ id }); } create(data: Partial) { return this.usersRepo.save(data); } } ``` TypeORM nggunakake kelas `@Entity` (dimapake menyang tabel) lan `Repository` yang bisa diinjeksikan kanggo query — cocok karo model DI ing NestJS kanthi natural via `@InjectRepository`. ## Integrasi Prisma ```ts // 1. a PrismaService wraps the Prisma client (and manages connection lifecycle) @Injectable() export class PrismaService extends PrismaClient implements OnModuleInit { async onModuleInit() { await this.$connect(); } // connect on startup } ``` ```ts // 2. inject it and use the type-safe client @Injectable() export class UsersService { constructor(private prisma: PrismaService) {} findAll() { return this.prisma.user.findMany(); } findOne(id: number) { return this.prisma.user.findUnique({ where: { id } }); } create(data) { return this.prisma.user.create({ data }); } } ``` Prisma ngasilke client sing fully type-safe saka file schema; sampeyan mbungkus menyang `PrismaService` sing bisa diinjeksikan lan nggunakaké menyang layanan sampeyan. ## Migrations lawan synchronize ```text ⚠️ NEVER use `synchronize: true` (TypeORM) in production — it auto-alters your schema and can DROP data. Use MIGRATIONS (version-controlled schema changes) instead. Prisma: prisma migrate dev/deploy manages schema changes via migration files. ``` ## TypeORM versus Prisma ```text TypeORM → repository/active-record patterns, decorators, mature, official Nest integration Prisma → schema-first, excellent type safety, great DX, growing popularity ``` ## Kepentingane Integrasi database iku penting — meh kabeh back-end nyimpen data, lan ngerti carane nyambung database menyang NestJS kanthi cara idiomatic iku pangaweruh praktis inti. Boro-loro ORM mayor cocok karo arsitektur NestJS kanthi rapi: TypeORM via modul official `@nestjs/typeorm` (nata koneksi, mendheskripsikan kelas `@Entity`, nginjeksikan `Repository` lewat DI) lan Prisma via `PrismaService` sing dibungkus bisa diinjeksikan (menehi type safety sing apik). Ngerti carane setiyeng koneksi, mendheskripsikan model, lan nginjeksikan lapisan data-access menyang layanan — nganggon logika database ing layanan, kapisah saka kontroler — iku fundamental kanggo ngbangun aplikasi NestJS sing nyata. Kritisle, ngerti prinsip **migrations-over-synchronize** (ora pernah auto-sinkronis schema ing produksi, ana bisa musnah data, nanging biyen nggunakake migrasi sing dikontrol versi) iku praktik penting kanggo keamanan produksi. Iki bahan saben-dinten, kudu-ngerti, amarga persistensi data iku inti menyang back-end development lan integrasi ORM iku carane aplikasi NestJS bener nyimpen lan ngambili data.