Nest.js Microservices Tutorial in 20 Minutes

In this short tutorial, I show you how to create a Nest.js project with Microservices along with an API Gateway.
Github Repo: github.com/mgu...
Nest.js Documentation: docs.nestjs.co...
Get my highly-rated Udemy courses at a discount here: michaelguay.de...

[@ChromaDotNova]

First time stepping into the realm of microservices - I still had some questions after reading the NestJS documentation so I went to KZbin, found your video, and after watching I understand the fundamentals a lot better. Thanks so much for taking the time to make this!

[@rafaelfranco7643]

Finally a good example of microservices using nestjs! Thank you very much.

[@Jasonjk74]

Great video and an amazing amount of practical info/learning packed into 18 minutes

[@illia_mikhow]

Loved the pace of a video. Short and filled with information. 10/10

[@itmax77]

I think I've seen you somewhere

[@FabioSilva-xd4nt]

Thank you a lot man. You made me understand some things that were difficult to me

[@lexNwimue]

Wow! Great video. Really commendable! I mean, in literally 20 minutes I've gotten a detailed, conceptual image of the entire NestJS Microservice technique

[@danielborges8857]

Your examples communicated some key concepts and clarified nest js implementation options. Thanks

[@satadhi]

On man you are so good. I liteally bought your udemy course. You are a great teacher sir

[@jeandedieuiradukunda6079]

this is awesome i now just got an idea of microservices

[@chrismantonuk]

Great, thank you - a lot clearer to me now! You covered everything

[@debasistripathy4459]

I DOUBT

[@ikr0525]

Thank you! Awesome video! In our company, someone was assigned to setup the microservices and I really did not mind to understand because I believed it was too complex for me. As long as the microservices were all set up, i just continued coding as usual. This video made it very easy to understand and I can now see why the dev who setup the microservices decided to go with certain approach. I'm curious about the authentication across different microservices, though. Can you make a video for that if possible? That would be amazing!

[@avimehenwal]

Excellent vide Michael, love your content and way of explaining things. Keep it up

[@mguay]

Thank you!

[@maksymbaranovskyi8362]

Thank you so much! Such a simple yet clear example.

[@vinimaciel]

Awesome video, you made it so easy to understand

[@danmarzo5508]

Muito obrigado pelo conteudo excelente! O quanto que eu fiquei procurando sobre microservices com api, so o seu video me tirou as duvidas, MUITO OBRIGADO

[@hollynderisse645]

Thank you very much for sharing this tutorial. It's well explained and very helpful

[@ayoubguismi4558]

As always simple and clear explanation, thank you michael !

[@mguay]

Thank you as always, Ayoub!

[@mguay]

Get my highly-rated Udemy courses at a discount here: michaelguay.dev/udemy/

[@alexsapon8769]

Nice example I would suggest you to use monorepos feature that Nestjs provides, quite smooth microservices architecture at the end, plus gives you ability to clean your codebase from code duplication such as dto's you're using across the services best regards

[@uchihaashura5021]

Hi but I'm quite struggle to exclude unnecessary dependency for each app, for example we add a new dependency for ervice A, but we don't need it in service B, when building docker image we are include all this dependencies, how we can exclude them to reduce docker image size ?

[@mcc12000]

@@uchihaashura5021 having a monorepo doesn't mean that you have a single docker image i guess.

[@sndro1]

Does this mean that I can share models across services? Do you have any recommendations for tutorials about this?

[@theaungmyatmoe]

@@sndro1 Model should not be shared to the others services. They should be domain specific to their own service. So that you have to attach service related domain object to your service

[@sndro1]

@@theaungmyatmoe I do understand that but how do I share typescript types for these models/services (so that the consuming service knows what it gets)?

[@PraneetNegi-n3i]

Can we use libs/common for Authorization and some other common utils like we do in monolithic project, using this microservice structure ? If Yes then please give me some references. Thanks

[@muratasarslan2359]

thanks a lot. very helpful. is there a way to avoid duplicating CreateUserEvent in all microservices?

[@millerbyte]

What's the point in using the event-based communication pattern if we have to declare / inject all the subscriber microservices (sample-analytics, sample-communication) within the publisher microservice (sample-backend)? Isn't one of the primary advantages of event-based communication the fact that the service publishing the event doesn't know / care about any downstream services that may subscribe to it? This seems like there's still tight coupling between services. For example, what happens if I want to add another service that cares about the user_created event -- will I have to modify the sample-backend to allow this? Seems like an antipattern. This isn't a criticism of you or the tutorial -- thank you for sharing! It's more a criticism of NestJS if this is how the expect you to handle event-based communication.

[@mguay]

This is a great criticism and I wholly agree. I’m making a new Microservices video that uses RabitMQ as the messaging broker which allows us to remedy a lot of these concerns around tight coupling. Thanks for watching!

[@millerbyte]

@@mguay Thanks for the reply, looking forward to the updated video!

[@abdelhalim731]

but this is good for communication between servers no?

[@bv5191]

I'm glad someone already asked this cause it is my concern as well. Having to inject the "microservices" just makes it a distributed monolith instead of a microservice architecture.

[@tesla1772]

i didn't understand how microservices get the event. http based api it is understood that port and ip is given but how does microservice listen to event

[@larswolter669]

How do you effectively test automate these event / message based applications?

[@eihsan94]

Would like seeing this deploy using severless framework and lambda

[@imranabdulmalik3591]

You're the best!

[@malkasoft]

Amazing tutorial! Thanks for sharing

[@Olixis]

How does the "sample-backend" knows that "COMMUNICATION" refers to the "sample-communication" microservice? As far as I saw the "COMMUNICATION" token is only at the "sample-communication" microsservice

[@muhammadsalikin3886]

by using ClientProxy, sample-backend which acts as gateway is basically the one who reach out to the other services.

[@EstebanHelgueroCardiff]

Awesome video!

[@Thikondrius]

Great tutorial simple, and clear. Good job. Btw can I ask what your vscode theme is ?

[@talhacoder5084]

that was so beautiful 🤯

[@mahmoudfathy6332]

Amazing man 👌

[@behradkazemi213]

great video thank you so much!

[@yousoffatomi]

thank you for record this video ♥

[@LasparkOficial]

Nice work!!

[@PeterAkaliro]

wow! so simple lol.... You are a life saver bruh

[@sg0101010]

Great video. Question: I'm getting a "no elements in sequence" from the getAnalytics call ? I'm on version 9.x.x

[@zackinfos5933]

thank you Michael for everything, well how do you compare this approach adopted by you, where you have added multiple nestjs projects to one aorkspace, which i found flexible, VS or compared to the one adopted by nestjs monorepo (apps)? well honestly i find this approach more flexible as i have said above for many reasons: - Scalability. - Teams and colaboration. - Multi-lang dev environment. - Database per microservice and the hustle of dealing with monorepos setup and configs for shared files and packages like prisma for example. - Avoiding limitations by any given framework, which makes you finding yourself dealing with solving problems by the same language often with the help of the same tools which results at the end of the same results, thats what stand agains the microservices principle and patterns.

[@hariharamoorthis3488]

Hi... Thanks for your tutorial... Can you please clear my doubt?.. can we call api endpoint of communication or analytics microservices?

[@thomasbalboa628]

WTF, the tutorial doesn't work, even when reproducing exactly what the author does, it bugs when sending the POST request in Postman. Even after cloning the repo and running both servers with 'nest start --watch', nothing happens. The request runs infinitely, and there's nothing in the logs.

[@Xeartoo]

Change the listening port on all back-ends. This should solve the problem.

[@henrycodingstack6952]

I am a bit confused here i thought the sample-backend which is acting as the api gateway is supposed to pass the incoming request to a microservice to handle, whatever business logic and then the specific microservice can emit an event so that other services that needs to do anything with be notified.??

[@nnu5510]

Great video, thank you.

[@okmylifeday]

Thank you! Very good for me.

[@hakanaki]

Please some question. - Why did you choose use TCP instead of GRPC and what are the benefits? - How do you host something like this 🥲🥲 - Is it possible to share code between services, like types or DTOs? Thank you for this video BTW, I've been struggling with this concept and you just simplified it in one short video. 👏🏽👏🏽

[@kanishkasuvarna7985]

+1

[@homelander973]

thank you a lot bro, it was really helpfull

[@shalandichannel]

Is there a way to use the TCP transport pattern with external apis that are not written with nestjs? And is it possible to use other TCP ports that are private to the microservices when dealing with TCP communication? Or must the traffic all go through the single "3000" port?

[@manorinfinity]

Thanks for the video. Loved it. It would be good if you could do a video on microservices and monorepo in nestjs. I mean how do you create a monorepo microservices project in nestjs where we have one API gateway for http requests and all the other microservices listens to events sent by API gateway without allowing http requests on their own.

[@mguay]

My new Ultimate Nest.js Microservices course will cover this! Stay tuned for its release in May.

[@verrymariyanto8377]

i learn a lota from this tutorial,, can you give litle bit explanation about how to get some return result about using this method,, if we using try catch in controller,, thx

[@Akim-z8t]

What is that theme? pllz

[@jithinjacob2181]

How can it handle parallel processing of requests in the backend, mostly i have seen people use Java /Python to work out the backend

[@maximcoding2667]

How is it different from with gateway api + createProxyMiddleware ?

[@cholasimmons]

Subscribed!

[@diegoalonso2832]

I have a doubt Is there another way to consume mi grpc service without an api gateway?

[@jafar1607]

Brother. Can we have a multi tenant example with nest js ?

[@romeobetances7964]

Great job!

[@danilopootaren4512]

I loved it !! Quick question, would this work the same with docker container?

[@ericww32]

Is there a way to grab any message pattern and put it into a variable?

[@ИванДрачев-ы3у]

When i run 'sample-communication' app (after 'sample-backend' is running) - i got an error that port 3000 already in use...Could anyone give me an idea?

[@navinmishra6038]

As the communication microservice by default listens to 3000 port, we need to make backend server listen to another port(eg: 3001). Then we can run both service

[@sumitpatil7084]

Hello Michael how can i use typescript in nestjs

[@temidayomichael4646]

Which one would you recommend between this pattern and the monorepo micro services pattern in your latest video and what’s the best practice in deployment and repo management? I think I like the monorepo more cos my team is small but I have no idea on the deployment. Thanks a lot!

[@mguay]

Really it depends on the differences between Kafka and RabbitMQ. I would also recommend a monorepo for smaller teams as it is easier to work with, but it is also makes deployment easier.

[@siamak.hatami]

Great, thanks.

[@xixayyumiko6766]

how do I do if I made the microservice apart

[@HarikrishnanM0]

At what situations we should go for a microservice architecture ? I am basically developing rest apis .So how can we make a decision on building a micro service ?

[@mguay]

Microservices help you manage complexity as the size of your application + team grows. For simple projects with one developer, they're not as necessary in my opinion.

[@HarikrishnanM0]

@@mguay ok got it

[@ninjatikeidu]

At first it didn't work for me, after a while I understood that I needed to establish the host and port when registering the ClientsModule, after that it worked correctly, tks

[@isaacnwankwo6634]

please How did you do that, I am facing the same challenge here. I

[@isaacnwankwo6634]

please never mind, I have figured it out.

[@raneanish21]

How to implement multiple messagepatterns?

[@minhazahmed128]

This is good but this is gonna take a lot spaces, why not using nestjs workspaces?

[@alvin3171997]

Hi Micheal, have you used any backend framework in the past? Like Fastapi etc. Just wondering what’s the pros and cons of using Nestjs. Thank you so much for the video!

[@mguay]

Good idea for a future video!

[@nanonkay5669]

Next, you show how to do it using a message broker

[@learning-new-everyday]

amazing

[@lialia3293]

Great !

[@miguecast]

Do you know that Guay is a very common 80's spanish expresión that means "cool"?

[@lardosian]

Could all these services be split into their own repo?

[@mguay]

Sure you could but I’d say that typically doesn’t follow the standard practice of micro services. At the end of the day though do what best fits your needs.

[@narrajayasri94]

I am unable to get the output can u guide me or respond to my comment. Plz

[@jazzdestructor]

Hey guys, What is the difference between emit and send methods?

[@sarunmrzn]

I believe emit actually sends a request to the ms but send just proxies the entire request to ms, correct me if im wrong

[@deliomarcosdacostajunior3036]

Thanks from Brasil ! õ/

[@Varshakumari-uz8uo]

Why I am getting listen EADDRINUSE : address already in use error.

[@foued619]

same problem, that's because both servers are trying to run on the same port (3000)

[@navinmishra6038]

@@foued619 As the communication microservice by default listens to 3000 port, we need to make backend server listen to another port(eg: 3001). Then we can run both service

[@yadneshkhode3091]

How to use request body in services? without passing the body in functions in controllers

[@mguay]

I may make a video on it in the future, but check out github.com/nestjs-steroids/async-context

[@SRPPixels]

when starting the communication server after running sample-backend. it is giving error that port 3000 already in use

[@SRPPixels]

I also cloned your github project. it is still giving the same error

[@cess_uyi]

Me too! Please how did you resolve this?

[@hakeemullahjan]

Still facing the issue after changing the PORTs.

[@akhil0227]

on sample-backend in main.ts file . await app.listen(3001) and on sample-communication main.ts file - Transport.TCP, options:{port:3000} . use postman to send request in localhost:3001

[@thaingocnguyen1015]

me too, i don't know why it can work on his machine @@

[@martinavalos1626]

what do you think about using prisma package for handling databases queries? did you ever use it ?

[@saurabhtalele1537]

🎉🎉🎉cool

[@umer.on.youtube]

Do not use a stupid max. Get on Windows.

[@nditahsamweld346]

Hi Michael Guay, what's your twitter handle. Nice job!

[@mguay]

Thank you! I don't have a Twitter though.