Skip to content
Hallway
0:00 / 0:00

#prisma#orm#knex

We need to talk about Prisma

Mehul Mohan

474K subscribers • 1 video on Hallway

YouTube
  • Recommended by 2 people: 2 in engineering communities.
  • Presented by Mehul Mohan, founder of Codedamn
  • May be out of date. The tools, versions or practices it shows have likely moved on.
  • An opinion. It argues one side of a question engineers disagree on.

Intermediate. Assumes working knowledge.

61K views3 years ago2 recommendations

Databases and dataWeb developmentPostgresSQLDatabase internals

Mehul Mohan explains why his team migrated away from Prisma to raw SQL and Knex, highlighting performance and serverless issues.

We migrated to SQL a month back and our biggest learning was to never use Prisma. Watch the full video to know what happened and how we found a solution. Read the full blog here: codedamn.com/news/product/dont-use-prisma Are you confused where to start coding/what to learn/what roadmap to take? Take this free 2 minute quiz: codedamn.com/career-path-quiz 👉 Checkout codedamn on social: ✨ Instagram: cdm.sh/ig ✨ Twitter: cdm.sh/twt If you found the video valuable, please leave a like and subscribe ❤️ It helps the channel grow and helps us push out more valuable content. ✨ Tags ✨ #coding #sql #migration #prisma #mongodb ✨ Video Tags ✨ Never Use Prisma We migrated to SQL. Our biggest learning? Don't use Prisma. Don't Use Prisma.

Why it's here

2 people recommend this

What people say. Engineers point to this video when discussing Prisma's performance issues, serverless overhead, and the trade-offs of using ORMs.

Moments people linked to

u/teraflipflopsin r/typescript • Recommends

On “What are the biggest gotchas/weirdnesses of Prisma?”

There were some issues regarding query performance and using Prisma in a serverless environment. However I believe that they are working on fixing this. This video talks about it: [video I think one of the gotchas of any ORM is that you don't write your own SQL so you don't have much control. Therefore it is hard to diagnose performance issues and it's much harder to do complicated queries this way. Personally I think Prisma works especially well in smaller apps where the data model is fairly simple.
7View on Reddit

u/TheBeardMDin r/node • Recommends

On “Which ORM should be used? (polling)”

If you're not familiar with Prisma issues, here it is: [video
1View on Reddit

u/TheBeardMDin r/node • Recommends

On “How risky is Prisma Postgres now ?”

stay away of prisma. [video
-2View on Reddit

u/rmirroin r/node • Mentions

On “Is this a valid reason to give up node?”

I just watched this today. I think they dumped prism as the ORM and switched to knex. Prisma may have been partially retained for schema definitions that knex doesn’t support. link to this video
1View on Reddit

u/TheBeardMDin r/node • Mentions

On “To migrate or not to migrate - is TypeORM really dying?”

Typeorm IS NOT DYING. It's used in production in so many projects. All the ORMs have issues, check this on Prisma: [video So in summary, they all have issues. Pick your poison. I like typeorm and it has clean syntax and it has been incredible... with few bugs indeed but nothing major...
1View on Reddit

u/_He1senbergin r/node • Mentions

On “What is React(compared to Svelte, Vue, ...) of ORMs?”

I think it’s prisma but also i think it has some problemes im currently using typeorm with nest and it does the job, the docs are not the best but meh…
-2View on Reddit