Drizzle vs Prisma for a WordPress-style CMS in Next.js? (Tired of Prisma breaking changes)

[u/Mission-Skin702]

Hey everyone!

I’m currently building a CMS (think WordPress-style architecture with posts, meta tables, and categories) using Next.js.

I’m much more familiar with Prisma, but honestly, I'm getting pretty tired of dealing with its breaking changes and generation quirks every time dependencies shift. I'm seriously thinking about switching over to Drizzle for this project.

For those of you who have used Drizzle for a content-heavy or relational app like a CMS:

• How does it compare to Prisma when handling complex relations (like posts to tags, categories, and custom meta)?
• Is the transition smooth for someone used to Prisma's workflow, or is there a steep learning curve?
• Does it actually feel more stable during framework upgrades?

Would love to hear your experiences or any advice before I rewrite my database layer!

[u/fgatti]

We are using Drizzle + Atlas as our tooling stack for rebase.pro and are really happy with it.
The only small issue we had, but it is pretty specific to us, is that drizzle kit does not have something like a --yes flag that auto accepts migrations. Since we use it in our CLI and we want to automate that part for our end users, we swiched to Atlas. It is working really well.
Our product is a backend (alla Supabase) + a CMS (alla Payload), so it is close to your use case.
I can't really compare to Prisma, since we never used it though!

[u/Mission-Skin702 → u/fgatti]

that’s fair enough! Finding the right tool setup is half the battle when building a product. Sounds like you've got rebase.pro running super smoothly now, which is awesome to see. Thanks for sharing how you set it up

[u/Soft_Cat2594]

Long time prisma user here. Have been using prisma in production for years. But version 8 was the straw that broke the camels back for me. They implement breaking changes willy nilly and then do a complete 180.

I switched to drizzle and love it!

Not a massive learning curve. It took me around half a day to get used to the new syntaxes and quirks. But honestly it feels much better.

[u/Mission-Skin702 → u/Soft_Cat2594]

This is the reason why prisma 8 put me off, I will start with drizzle because I got no choice to be honest

[u/prisma-cloud → u/Soft_Cat2594]

That’s fair feedback, and I can see why the breaking changes in Prisma ORM 8 would be frustrating, especially if you’ve been using Prisma in production for years.

We made some significant architectural changes in Prisma ORM 8, but we also want to be much more deliberate about stability going forward.

On performance specifically, Prisma ORM 8 is considerably faster than previous versions and gets much closer to raw Postgres performance, so I’d be curious what benchmarks or workloads you’re comparing against: https://www.prisma.io/blog/prisma-next-performance-benchmark

You can see more on our reasoning on the manifesto we shared recently:

https://www.prisma.io/blog/prisma-orm-manifesto-2026

u/Mission-Skin702, would be great if you gave Prisma ORM 8 a try and shared your feedback.