I've used both, and Prisma is way nicer to work with IMO, especially if you don't know SQL super well. With code generation, you can explore very easily the types of queries that you can make, and also having type safety in your queries helps you write them much faster. I also felt like, with TypeORM, I would run into stupid, horribly documented problems all the time. The only edge I'll give on TypeORM is validations were nice. But truth be told, with a library like Zod or yup, you can get plenty of great validation pretty easily. Your code just winds up looking a bit different.
Problem in prisma : 1. you can only have one prisma schema file, imagine how big it is when the app contain 20 model. 2. There is no hooks for model, 3. You can't extend the model class 4. Soft deleting is possible, but too verbose 5. There is no global scope utility
Tnx for this video. I actually tried both, and I gotta go with Prisma 2 on this one. Usually I run into problems with setup (nothing bad, just some googling required). Not with Prisma 2. But, what really made me switch was rumours that TypeOrm was no longer maintained, with an old old roadmap that still wasn't implemented etc. (there were also some rumours that it wasn't production ready on reddit) So my question is: is TypeOrm back on track (did they get funding, are they solving issues, etc)? I used it and it was pretty good, but I don't know if I'd trust it for anything serious/professional if it's not still going on. It's a great pity, since I loved it much more than sequelize or microORM.
Thank you for this video. Please can you make a video showing how to dockerize a Nodejs backend project that uses prisma and postgres. I have been struggling to get prisma to work well in a dockerized environment. Will really appreciate it
Prisma is better funded and it shows in the tools and docs, but class based schema is still far better. Prisma also has limitations with mongodb where it would need to be run in a cluster so no support for a simple local mongodb instance in Prisma.
Prisma doesnt supports ts_vector. Aswell there is no support of rawWhere conditions (which really helpfull when you are working with posgres extentions, or some other specific cases). But TypeORM has.
This is really useful video. I heard about when we deploy production with Prisma is pretty annoying because it needs some specific library to work on the web server. Is this true? And like, how annoying is this? Compare to TypeORM, does it have any kind of issues as well? Thanks!!
Thanks for the informative video! Just some idea for your future content: It's sometimes a bit hard to follow you because of the way you cut your videos. Often, between sentences you would immediately start the next sentence. But for comprehension and in usual speech, people leave longer breaks between sentences. I think leaving those breaks would make your videos even more enjoyable to listen to. Again, great content, keep it up!
![ทุกครั้งที่หลับตา (Lucid Dream) - AYLA's [ Official MV ]](http://i.ytimg.com/vi/4i1OBAQyv58/mqdefault.jpg)
Never heard anyone say 'CLI' as 'klee'. Nonetheless, informative video.
Nor have I heard anyone not use O-R-M
@@asiraky Also rep-oh
i thought he was text-to-speech when that happened xdd
@@texmex810 i read as ri-poh
klee im dead 😂😂😂😂😂😂😂😂🤣🤣
I've used both, and Prisma is way nicer to work with IMO, especially if you don't know SQL super well.
With code generation, you can explore very easily the types of queries that you can make, and also having type safety in your queries helps you write them much faster. I also felt like, with TypeORM, I would run into stupid, horribly documented problems all the time.
The only edge I'll give on TypeORM is validations were nice. But truth be told, with a library like Zod or yup, you can get plenty of great validation pretty easily. Your code just winds up looking a bit different.
prisma has alittle higher gap to get going. But once you get going. It feels professional. Typeorm is more a hobby library.
Problem in prisma :
1. you can only have one prisma schema file, imagine how big it is when the app contain 20 model.
2. There is no hooks for model,
3. You can't extend the model class
4. Soft deleting is possible, but too verbose
5. There is no global scope utility
I'm glad you used the logo I created for TypeORM
honestly buidling a db using the prisma schema is so easy and intuitive and the auto generated types. things a beast.
Oh man the CLI
Keep it up dude, you're doing good. Enjoyed your vid, keep'em coming
How to manage a "union" or a "polymorphic relationship" with Prisma, it seems to have a poor support for that?
Tnx for this video. I actually tried both, and I gotta go with Prisma 2 on this one. Usually I run into problems with setup (nothing bad, just some googling required). Not with Prisma 2.
But, what really made me switch was rumours that TypeOrm was no longer maintained, with an old old roadmap that still wasn't implemented etc. (there were also some rumours that it wasn't production ready on reddit)
So my question is: is TypeOrm back on track (did they get funding, are they solving issues, etc)?
I used it and it was pretty good, but I don't know if I'd trust it for anything serious/professional if it's not still going on. It's a great pity, since I loved it much more than sequelize or microORM.
Awesome overview, thank you!
Great Video , Thank You.
Thank you for this video. Please can you make a video showing how to dockerize a Nodejs backend project that uses prisma and postgres. I have been struggling to get prisma to work well in a dockerized environment. Will really appreciate it
My preference is MikroOrm
It looks really nice and similar to SqlAlchemy which is robust and has very close syntax to the SQL.
It's slower than TypeORM, and more complicated in a lot of sense
Did you actually say KLI? Great video overall but please, ORM and CLI should be pronounced as abbreviations.
Great video! Thanks!
the relation joke at &:10 was so bad it became funny XDDDDDD
Thanks for this 🙂
Great explanation. But my man my man, what the heck is a 'klee' and a 'reppo'
Prisma is better funded and it shows in the tools and docs, but class based schema is still far better. Prisma also has limitations with mongodb where it would need to be run in a cluster so no support for a simple local mongodb instance in Prisma.
my eyes bled when they saw typeorm schema
Prisma doesnt supports ts_vector. Aswell there is no support of rawWhere conditions (which really helpfull when you are working with posgres extentions, or some other specific cases). But TypeORM has.
Kleee. 🙌🏻
Thanks brother
Thanks for the vid. It would be nice if you do comparison between Knex + Objection, Prisma, TypeORM and MikroOrm and Sequelize.
Heads up the maintainer announced on the issue tracker that objectionjs will no longer be maintained
@@mgan59 Thanks
This is really useful video.
I heard about when we deploy production with Prisma is pretty annoying because it needs some specific library to work on the web server.
Is this true? And like, how annoying is this?
Compare to TypeORM, does it have any kind of issues as well? Thanks!!
Yes if deployed on cheaper web hosting then it will cause issues.
I deployed my application on aws due to this problem only.
Thanks for the informative video! Just some idea for your future content: It's sometimes a bit hard to follow you because of the way you cut your videos. Often, between sentences you would immediately start the next sentence. But for comprehension and in usual speech, people leave longer breaks between sentences. I think leaving those breaks would make your videos even more enjoyable to listen to.
Again, great content, keep it up!
It doesn't work on inteliJ? Wow even in Vim works awesome with the LSP + Format (Native).
really nice video
What about performance?
Pronunciation please. Dude I can watch your videos. I barely made it 30s. It's an acronym, O.R.M., object relational mapping, nor orm or arm.
Prisma is amazing.
Lmao CLI...
CLI xD
The link to the repo is broken btw
The latency when I use Typeorm is better than Prisma.
Had to stop watching the video at 'Klee'.
Ormmm and Kleeeee???
What about sequalize
Been using both of them but I got to say Prisma too much overhead
[o - r - m] not {orm}
like [i - o - s] not {ios}
and like like [mac - o - s] not {macos}
I was stuck it because you're repeated too much
I've never heard someone pronounce it "orm". There is a reason ORM is capitalised, you're meant to spell out each letter.
Is this a computer voice?
Klee? What😂😂
The repository does not exist
Sequlize orm is dope 👍
Their docs are dogshit though
klee.
Stop coming up with your own jargon. `klee` for CLI, and `orm` for ORM. Are you kidding me?
Look
klee 💀
just don't use TypeORM it's pain in the ass. IT IS BAAAAD!
Fantastic video! Thanks!