intermediate

Prisma ORM

Model data with Prisma schema, generated client, relations, migrations, and transaction APIs in TypeScript backends.

Prisma interviews combine schema design, generated client usage, migrations, relations, and transactions. Type safety helps at compile time; production still needs SQL visibility and connection discipline.

Subtopics: schema, client, migrations, relations, transactions.

On interviews: explain `select` versus `include`, migration review habits, and which transaction API fits a money-transfer invariant.

Common pitfalls: over-including relations; many PrismaClient instances; drift between schema and deployed database.

The trade-off is schema-driven DX versus database operational ownership.

Checklist:

Model relations and indexes in schema.
Observe SQL on hot paths.
Use deploy-safe migrate commands.
Scope transactions to short invariant work.