How To Get Started With NestJS, GraphQL, Prisma | Building An API With Nestjs, GraphQL And Prisma!

In this video, you will learn how to setup NestJS, GraphQL, Prisma and Postgres.
After that, we will be building an API with CRUD-(CREATE, READ; UPDATE, DELETE) functionality.
In order to follow this tutorial, you should make sure to have Docker Desktop installed, because we will be using it to spin up our Postgres database instance.
I hope this is helpful. Thanks for watching :)
Do you need something from Amazon? If you want to support my work and motivate me to produce more & better programming content, use my Amazon-Affiliate-Link.
It does not cost you any extra money, but I get a little commission, whenever you buy anything via this link. It means the world to me 😊
🌟 Affiliate-Link: amzn.to/3QaXk0A
#nestjs #typescript #backenddeveloper

[@prodrigu75]

It is a basic tutorial, however it is an excellent tutorial for a newbie to Prisma, Postgres and GraohQL. Congratulations and greetings from Santiago de Chile.

[@RolandAyala]

Thanks for the rundown, very helpful, and super appreciated! Also, your desktop is a sight to behold!!

[@BromanThings]

In a WHOLE SEA of 3 hour tutorials on this stuff, you've struck genius here. You explained no more, and no less than absolutely necessary for me to follow along, while actually understanding the 'why' behind it all. As someone brand new to nest, graphql, and prisma all at once, I'm just astonished and grateful. One of the best programming related walkthroughs / tutorials I have seen in a very, very long time. Thank you so much for making this

[@arisetyo7]

This is so helpful. Thanks! Cheers from Indonesia 🍻

[@okeyshourovroy2769]

Can you please make a video on apollo server express and reactjs refresh token implementation?

[@codingislove3707]

Hey, I will see what I can do. Currently I am working on a little online shop video with Nestjs, GraphQL and NextJs :)

[@carlosgabrieldev3900]

thanks for the excellent tutorial, really helpful

[@navy4450]

What is that auto complete

[@arupde6320]

be regular

[@otaviodallo622]

great video

[@dawid_dahl]

PARTY HARD! 🎉

[@bestelectrocity]

Wow nice tutorian, is it possible to do " Private Chat App " using NestJs, GraphQL and Prisma and React as a front end side. Thanks :)

[@ashishkmr]

Bro how many folders you got on desktop, lol Cool video tho

[@codingislove3707]

Haha, you are absolutely right. A lot of stuff going on my desktop. I think for the next video, I will clean it up 😁

[@макскупр-ш4у]

cool.. very very cooooolll !!! thank you for that amazing content!

[@omnilothar]

the create todo in the service file, why use async await again, what if you dont use it?

[@hpn1427]

Thank you for this, really helpful

[@kacperkrasnodebski5896]

Wonderful Thanks!

[@WOYGx1010]

Thank you for this !!!

[@brandonpetty3849]

codingIsLove, my heartburn with this solution is that you get the worst of both worlds. You do a "code first" AND a schema implementation, due to Prisma. Not only does this require you to do double the work and make sure both systems are in sync, it appears to make the Entity concept almost useless. Ideally my Entity would construct my schema so that I don't have to manage this in two places, like .Net's code first Entity framework. Any thoughts? I am new to NestJS and GraphQL, so I may be missing something. Is there a better ORM that ties in more seamlessly with Apollo? Also, I wrote an OData layer for Primsa and found Prisma lacking the ability to many things that would also affect GraphQL. Am I correct to assume that Apollo gets around that by using raw SQL queries and in this Next/Apollo/Prisma example, Prisma is only used really to manage database migrations? Any recommendations on how to do a true code-first implementation with Nest and Graph would be appreciated.

[@olli_]

Maybe too late, but TypeORM lets you do the true code-first approach. You just add some more Entity/Relation decorators into the already existing entities. You also have to import one module (i think) and inject repositories into their respective services. I would say that this approach showcased by codingIsLove is good for understanding the basics, but I also prefer the true code-first approach.

[@ArthurKatrushko]

Thank you man 👍