So, I'm starting a simple Express project, but we intend to eventually grow it, monetize it, and support it for a long time. But this project will also work as a portfolio project.

Should I use Prisma, TypeORM or something else? My guess is that since it's a simple project, it shouldn't matter that much, queries shouldn't be that complex for now at least, so I'd say the main question is, what ORM would improve my cv the most?

I’m building a backend with NestJS + Fastify + Supabase PostgreSQL and I’m trying to decide between Prisma and TypeORM as my ORM.

My main concerns are:

• Future-proofing (I don’t want to regret the choice later)

• Performance (good performance that won’t block me as the app grows)

The app is a hybrid of e-commerce + social media, with features like:

• Auth: Sign up, Sign in

• Social: Followers, Following, Posts, Likes, Trending

• E-commerce: Sell, Buy, Orders, Cart, Wallet, Earnings

• Messaging: Chat

• Profile Features: My Posts, Library, Settings, Notifications, Requests

Which ORM would you recommend for this stack and why?

I know each has its strengths and drawbacks, I needed a type safe ORM that I can use with typescript and I ended up with these two. Has someone worked with both? What is the most featured in terms of queries, migrations, seeding, etc? Which provides better programming experience?

Even if you live on Mars, you couldn't escape the big Prisma ORM hype

How is Prisma different than 'traditional' ORMs (TypeORM, Sequelize)? is it better? is it now the supreme choice for your next project ORM?

My new blog post covers these questions with code examples and numbers. It also includes a short hello-world section to give you a sense of how Prisma syntax looks like

Am I an ORM expert? Not at all. Although I have vast experience with databases, I'm writing from the perspective of a casual developer who seeks the right ORM for his next project. Hope you like it

https://practica.dev/blog/is-prisma-better-than-your-traditional-orm

I'm building the skeleton for a node.js enterprise-level application. And when it came to the ORM (with Postgres DB) I started with Prisma for all good features I read about it, especially after having hard time with Sequelize.

Unfortunately, my first issue I faced with Prisma is the lack of support for multi-files schema which broke the MVC pattern we adopting in our project.Then, I faced another issue which is lack of aws secret manager's support as Prisma only supports using .env files .

I need your recommendation of an enterprise-level ORM that is NOT SO COMPLICATED (which is against the whole point of using ORMs) and does support the above mentioned features.

Thanks.

I used to spend a lot of time working around some of Prisma ORM’s limitations by building complex wrappers on top of it. Eventually, I realized that creating a full alternative was the only way to address those issues cleanly.

That turned into ZenStack v3, which aims to be (almost) a drop-in replacement for Prisma. If you’ve felt limited or frustrated by Prisma lately, this might be relevant.

[DISCLAIMER: I'm the maintainer of the tool mentioned here]

What it provides:

• Prisma-compatible schema and query API

• Both a high-level ORM API and a low-level SQL query builder

• Extra capabilities like fine-grained access control, polymorphic models, typed-JSON fields, etc.

• A modular plugin system for extension and customization

Love to hear from others: What are the biggest gaps or pain points you’ve hit with Prisma?

For a personal project I'm looking for a modern nodejs ORM or a query builder. I've done a lot of research and it's hard to know what's the best so I've done an excel spreadsheet :

So far I have tested Drizzle and Prisma :

- Drizzle : I liked the simplicity and the fact that it's close to SQL. But I disliked a few things. Most of it is linked to the documentation and feedback from the CLI. First of all the maintainers don't even speak english properly so the documentation feels a bit low-cost. And most importantly, the Drizzle-kit CLI doesn't even give you any feedback when there is an error. It just stops without doing anything.

- Prisma : I tried it because ChatGPT told me it was the most popular and modern. I really liked the documentation and the CLI gives me good, verbose feedback when there is a problem. My only worry is that it's made by a company who seem really desperate for money because they are pushing a product that nobody cares about (Prisma Postgres).

What are your opinions? Should I stick to Prisma? (so far my best choice, but i'm open to alternatives).

Hey all,
which ORM do you prefer to use in Next.js Drizzle ORM or Prisma and why?

I kept going back and forth between the two for a while, so I wrote a deep-dive comparison to help anyone else who’s stuck deciding instead of actually building their product.

In the end, I went with Drizzle since I’m pretty comfortable with SQL and really like how lightweight it is.

Full read: https://medium.com/@codabu/drizzle-vs-prisma-choosing-the-right-typescript-orm-in-2026-deep-dive-63abb6aa882b

We used TypeORM for some projects, but I don't like that we need to use classes and I'm also not a fan of annotations.

Prisma looks very attractive with its type safe client and the migrations that it offers.

Is it a viable replacement for TypeORM for projects that 2 to 3 people work on for 3-6 month? Anything we need to consider?

I have been using Prisma, and im satisfied with it even though i had a few rough understanding especially when started. However i have been hearing about other alternatives like Drizzle, and contemplating wether it's worth my time to change after heavy use with Prisma ORM

Hello, I'm a developer working with the nestjs framework.

I have a question and would like to get your opinions and help.

I know that TypeORM and Prisma are the two most popular ORMs used in nestjs. I've been spending several days debating which one is better.

I'd like to hear your opinions.

Planning to use one of these. Thoughts guys? Last thread I saw was 5 months ago. Things evolve quick.

for both SQL and noSQL.

So, it's been 10 months since the last post on Drizzle vs Prisma. What are your thoughts now? Is Prisma the "Go-To" ORM for Node.JS ecossystem or there's a better one?

I know this has been asked many times, but maybe there's a new ORM in town.

I'm looking for an ORM with the following features:

• full typesafety

• schema reflection from existing database

• migration based on diff of current db vs last migration file state

• autocomplete and type checking on relations

[Edit] I don't know why I am being down voted for asking this question ?

Now I see node developers prefer prisma over other ORMs .. why ?