Hello guys, how's it going? Welcome back to my channel, and in today's episode, we're going to be comparing the three most popular ORMs in the JavaScript ecosystem. Now, we're going to be specifically talking about Prisma, Sequelize, and TypeORM, which I

know many of you might have heard of in the past. I've made tutorials on the three of them in my YouTube channel, so if you want to check those out first, you can go ahead and do so. But for those who don't know, an ORM is an object

relational mapper which basically allows us to translate database logic into simple JavaScript code. So in this video, we're going to be looking at pros and cons for each of the three different ORMs and also, more importantly, discuss specific use cases in which you might

want to use one of them over the other. So if you're about to start working on your next big project and you're unsure about which ORM you want to use, stick around for the video, and I'll tell you in the end. And before we get into the

video, if you could leave a like and subscribe, I would massively appreciate it because it will help push my videos to more people, and I would be eternally grateful if you could do so. So with that in mind, let's get into the video. [Music]

[Applause] [Music] [Applause] Okay, let's start right off the bat with Prisma, which is the ORM that seems like everyone's talking about nowadays. Well, Prisma is a modern and lightweight ORM which supports TypeScript out of the box.

its syntax in my opinion is very clean and intuitive, and it's TypeScript. It's generated TypeScript types make it extremely safe to use in any application. This segues into the first pro that Prisma has, which is the fact that it has really good support for TypeScript. If

you've watched my video on why you should always be using TypeScript no matter what use case, you would understand that TypeScript is extremely important in any kind of application nowadays. The only excuse for not using TypeScript in my opinion is either if you're making YouTube tutorials where

people might not know TypeScript and might be more familiar with JavaScript, or if you are a beginner learning JavaScript because it's totally understandable and it's how I learned as well. But if you're anywhere near intermediate to advanced and you've been

working for a while now, you should be working with TypeScript because it is necessary in any application now. Not only does Prisma have really good support for TypeScript, but it also has a fantastic developer experience where they provide a lot of different software and features such as Prisma Studio and

even a visual interface for your own database. Now I personally never used Prisma Studio, so I can't really vouch for that, but I've heard about it and I've seen people using it and it looks kind of cool. But um, it's definitely an

addition that you have to take into account. Now the final positive thing I want to talk about related to Prisma is the fact that nowadays it's been gaining a lot of notoriety, like people have been using Prisma in their own tech stacks.

and it's been gaining a lot of traction because of how TypeScript has also increased in its use in the past year and a half I would say. I'm not the kind of developer that just likes to follow trends because I think that it's not the best way to do it.

especially in an industry where everything changes so quickly. This is clearly evident by the fact that it took a while for me to even make any videos on Next.js because I really took my time to learn it, to perfect it, to understand uh how to work with it and um to then do

it because I didn't want to just make a video on it because it was a trend. But at the same time, you have to choose technologies that are popular because when you run into any bug, when you run into any problem, having a big community online, a lot of questions on Stack

Overflow, a lot of data on ChatGPT that you can ask for to solve your bug, that's that's necessary. Because if you're using a like a an unknown library or ORM out there and you run into a problem that no one has ever run into in

the internet, how are you going to solve it? You're gonna have a lot of trouble. So I think the popularity of Prisma nowadays is definitely something that should be taken into account. Now that can also be seen as a con in my opinion because Prisma is actually newer

compared compared to TypeORM or Sequelize. I believe it was released in 2016. So maybe it might be gaining a lot of traction and a lot of people talking about it now, but at the same time there hasn't been enough time of a huge amount

of people working on it to have as many resources similar to TypeORM and Sequelize. What I'm saying is if you're going to be building a project that is for the future, maybe think about using something that you might see being projected to be more popular in the

future, like Prisma. Now, what about TypeORM? This one I really like to talk about because if you've seen my video on TypeORM, you know that I really loved it. I believe TypeORM is the most flexible type of ORM in that it can be used in

both Active Record and Data Mapper patterns. Now, again, I want to emphasize that maybe a big deciding factor for you maybe the syntax. And I really enjoy TypeORM's syntax. But one of the major pros for this specific ORM is that first, it supports a very wide variety of

databases out there. It is very flexible on the architectural pattern you you prefer to use. And if you're working with transactions, it has a very robust support for them. Now, although I do like the syntax, I do think that the learning curve can be a little bit harder than, uh,

Sequelize and um Prisma. It starts to specifically get hard when you get into a little bit more advanced stuff. So I would say that that should be taken into account. It's not impossible to learn. None of this is impossible to learn. All of them are very

similar in a lot of ways, but I was just pointing this out in case you're just looking for something quick to use and you want to learn something easy. I would actually say the easiest one to use is probably Sequelize, but I'll get into that

later but Typeform is the hardest one in my opinion, and obviously the major negative with Typeform is the fact that although it does have support for TypeScript, it's not even close enough to what Prisma provides because Prisma was built with TypeScript in mind. I'm not

sure if Typeform was, but at least with the developer experience with the syntax notation, I know Prisma is fully completely supported supporting TypeScript and the Typeform, I don't see the same type of support. So that's definitely something you should take into account. Now finally we arrived at

SQL, Sequelize, and SQL. Uh, let me know if I'm wrong, I'm not. Don't call me on this. I think it's the oldest one because the reason why I think that is because it's the first one that I've heard about. So in my view, I see it as the oldest one

because back when I started coding, uh at least using ORMs, not coding in general, but when I started using ORMs and looking to choose one, Sequelize was the biggest one. It was what everyone was using or it seemed like it at the time. So there's definitely a lot that I can

talk about with Sequelize because I used it with so many courses and videos and and projects that I've done in the past. So this is definitely something that I can talk a lot about. Now in its core, uh Sequelize is just a promise-based ORM

that works in Node.js, and it's it supports the traditional promise-based API requests for handling any kind of database operations. Now the two main benefits that I would say for Sequelize, and to this day I still think they are important to take into account although

I don't use SQLizers anymore. The two main benefits are the fact that it definitely has one of the biggest varieties of database compatibility out there, similar to TypeORM, and also the community. It's, I believe, the biggest community out there. And because it is one of the

oldest ones, and it was massive back when I started. Um, so I never had any trouble like fixing anything when I've had trouble, uh, with bugs on something like Prisma because I couldn't, I found it harder to find someone who had the same bug as me

when it's with Sequelize, I didn't have any trouble whatsoever. Now, the syntax and annotation for Sequelize really sucks in my opinion. It's very verbose. A lot of times to do simple queries, you have to write a lot of things. It's definitely not as

easy and as simple as something like TypeORM and Prisma. So, that's definitely something you should take into account. And the worst one is the fact that it doesn't really have any good support for TypeScript. It leaves Sequelize to be a very

um, JavaScript-based form, uh, because that's what everyone used back then. But specifically for that, I think it is something that people have been steering away from because of how big TypeScript has become in the web developer community. The thing is, it doesn't matter if

I tell you the pros and cons, uh, it's still very confusing to know when exactly you should use each of them. Now, that's up to you. However, I am going to provide you my insight on when I would believe it would be best for you to use

any of them so I would say that this is how it's structured I would put Prisma and Typeform together but the way I would look at it would be if I'm working on something that I don't think will take a long time um or something that uh I won't be

working that much in the future or something that will just last a specific amount of time just a normal project and I don't want to learn Prisma or I already know Typeform I would choose Typeform now if it were working with anything related to TypeScript that is

probably something that you want to build upon and continue working in the future I would choose Prisma so those two is it really depends on whether or not how you see the future of the web developer industry and on the fact that which of those you actually already know

if you already know Prisma stick to Prisma if you already know Typeform if you're interested in that I would try to learn a little bit of Prisma but I would still stick with Typeform because Prisma is one of my favorites now you might be

thinking what about SQLite well SQLite I would say only use SQLite if you're working on a project that already uses SQLite and you're going to be uh working with it anyway so like in a company that um that uses SQLite and you have to learn

it to to work or if you want to use a specific feature or specific library that originates or is related to SQLite specifically now in any other kind of situation I would recommend Typeform and Prisma for sure although I love SQLite

as well I would say those two are better options I might be asking oh what about so now I know you might be thinking as well like oh you didn't really mention uh micro-ORM or what about um Objection.js or what about Mongoose now those options are good but first of

all micro-ORM and Objection.js are not as popular as Prisma, TypeORM and Sequelize so that's why I think those are second plane to to to the other options because most people out there would probably want to use the ones with the bigger community so that's why I didn't really

gave too much too much attention for those and if you're asking about Mongoose well that's not actually an ORM that's an actual ODM it's a little bit different so that's why I didn't because specifically for MongoDB so it's a

non-relational database but the options that I gave although you do have support for non-relational databases as well they have way more support as well for relational databases so that's why I didn't mention Mongoose or anything related to MongoDB so finally after all

of this review which one would I personally choose well if I were to start a project right now I would have to go with Prisma and it's obvious right it's obvious I've been using Prisma for over two years I believe um and I've been enjoying ever since I

did step back and use TypeORM for one project and I there was a period where I was like oh yeah TypeORM is amazing it's way better than Prisma but then I got back to Prisma it really depends on what what what what you're using in the

moment right I personally love to code on whatever I'm coding in the moment I always think it's the best thing in the world but then I switch it and I hate to switch it up but then when I do I realize that that other thing also has a

lot of features that I personally love so that's why don't use my opinion as a fact you know if you want to use TypeORM use TypeORM if you want to use Prisma I use Prisma if you want to use Sequelize that's just a wrong opinion no

I'm joking obviously but uh I'm saying like choose whatever you think is the best option based on what you want by using as much knowledge as you can gain from this video or any other video out there and then make your decision that's that's my opinion this is it for today's

video I really hope you guys enjoyed this video If you enjoyed it please leave a like down below and comment what you want to see next subscribe because I'm posting twice a week um if you're interested to see my channels just put notifications on because uh you it will let you know

exactly when I post if you want to check out all the gear that I use in my YouTube videos those lights in the background the camera the light that I'm using it's all in the description a link to Amazon if you're interested in buying

them and yeah that's that's basically it I really hope you guys enjoyed it and I see you guys next time [Music] [Applause] foreign [Music] [Applause] [Music] [Applause] [Music]

Prisma Vs. TypeORM Vs. Sequelize | Which is Better?

Prisma Vs. TypeORM Vs. Sequelize | Which is Better?

Scripts