This content originally appeared on DEV Community and was authored by Alex Escalante
When we first decided to use Prisma ORM for one of our Node.js services, I was genuinely happy with the choice. It offers a very ergonomic API—“friendly” at first glance, though you still have to figure it out—and it allowed my team to work without deep SQL knowledge.
But then, things changed.
As we got deeper into SQL, started using stored procedures, and explored more of PostgreSQL’s powerful features, Prisma began to feel more like an obstacle than a solution. Instead of facilitating our workflow, it made working with these advanced SQL features more cumbersome.
One thing that really started to bother me was the way Prisma applies magic to return types. It makes them practically impossible to share seamlessly, for instance, with my React clients. I still had to manually define all my DTOs, which felt like a step backwards. Maybe I was naive to expect otherwise, but for a while, I even considered writing my own Prisma plugin to generate DTOs—an overly complex path, to say the least.
So, when the time came to build a new service backed by PostgreSQL, we decided to take a different approach. Enter Drizzle ORM.
Drizzle is simpler. It feels more like writing SQL. There’s no overwhelming magic, just solid TypeScript support that actually helps rather than gets in the way. Sure, I still have to write my DTOs by hand when needed, but at least I’m not stumbling through Prisma’s enchanted forest of abstractions.
In the end, I’d rather have control than illusions.
This content originally appeared on DEV Community and was authored by Alex Escalante
Alex Escalante | Sciencx (2025-03-05T01:00:34+00:00) From Prisma to Drizzle: Shedding the Magic, Embracing SQL. Retrieved from https://www.scien.cx/2025/03/05/from-prisma-to-drizzle-shedding-the-magic-embracing-sql/
Please log in to upload a file.
There are no updates yet.
Click the Upload button above to add an update.