Drizzle ORM is the database toolkit I adopted in early 2024, replacing Prisma across my projects. The migration was one of the more painful technical decisions I documented on Twitter.
The Migration
In February 2024, I moved from Prisma to Drizzle for aperturs: “moving from t3 to turbo repo and @prisma to @DrizzleORM. its gonna be a good ride.”
The process was difficult. I noted several missing features compared to Prisma: no updatedAt field, no custom unique generators like nanoid, no delete cascade. “Hot take: migrating code base is painful experience, that’s it. Just got released from the pain.”
I ran 12 database migrations in a single day. I found a silver lining in having no users: “Sometimes I feel having no user in the early stage is also good, coz I can tweak my database as many times as I want and lose data and be fine with it.”
Ongoing Use
Despite the rough migration, I became a Drizzle advocate. By August 2025, I was excited about the v1 release: “So @DrizzleORM version 1 is finally coming, it has already beaten Prisma by a lot, idk what will happen now” (14 likes).
I use Drizzle across my projects alongside the T3 stack.