Drizzle vs Prisma: the verdict after a year
Drizzle gives you SQL with types. Prisma gives you a query builder with migrations. The right answer depends on whether your team writes SQL fluently and how much they value the migration tooling.
I shipped a year of production code on each. They are both genuinely good. The choice is less about which is better and more about what your team is going to do with it on a Tuesday afternoon.
Drizzle wins when you have engineers who think in SQL. The schema-first approach, the explicit joins, the closeness to the database — it all rewards SQL fluency. The codegen is fast, the bundle is small, and the runtime overhead is near-zero. Migration tooling is improving but still trails Prisma.
Prisma wins on developer ergonomics for teams that don't want to write SQL. The query builder is genuinely productive, the migration story is mature, and Studio is a real tool. The cost is a heavier runtime, more abstraction over performance, and a generated client that ships ~3MB to your serverless cold start.