Hey Michael, I followed your tutorial on nest js microservice using RabbitMQ, but I did not find if you used service registry. My idea is to have an auth microservice and an Api gateway app listing on 3200 that essentially work as a proxy forwarding request to auth. I looked online, most of them were too complexes. Can you help?
Wow this was amazing! Thanks so much for teaching us all of this again! As always lots of knowledge gained from watching your videos. Many thanks! What I learned is that the path a request goes through in order is... 1) Middleware - For things like authenticating a user 2) Guards - To check a user is authenticated before getting to the controller (manager of the task) among other use cases 3) Interceptor (before) - Can be used to log the method, url, userAgent, ip, controller name (ie., AppController), controller handler/method name (ie., getHello). Can also be used to transform incoming data 4) Pipes - Can be used to freeze parameters in the request so it isn't mistakenly changed in the code. Also validate input data, transform input data, etc. Typical usage is validating request parameters with built in NestJS pipes like ParseIntPipe, ParseArrayPipe, ParseUUIDPipe 5) Route handler - The "manager" that tells the provider (ie., service/worker/task implementer) what to do 6) Interceptor (after) - Can get the response and status code after handled by the control handler (ie., the method/function inside the manager). Useful for logging. Can be accessed via next.handle().pipe(tap(res=>{})) 7) Exception filters - To log errors internally or change the error response into user friendly wording for better UI Then it becomes a beautiful response Wooh! Just wrote the above to summarize what I learned - all info from going through this video. Thanks again and looking forward to your future videos! And ofc I gave your video a like as it's very helpful.
this is so great, been trying to figure out how I'm gonna get all the userIds to track operations and permissions. Gonna watch this properly next week and refactor my code.
This is a useful example to quickly understand the concepts of NestJs. I had forgotten all of it as I didn't use it for few months. Now trying to quickly revise the concepts and also understand other things which I had not used before. Your videos have been very helpful!
I just got some lessons on good architecture here :) The request service and freezing requests, am definitely applying that onto my current toy project and beyond. Thanks a lot Michael
Great video, you deserve many more subscribers, keep up the great work. I love it that you take the time to keep going through the different ways that features can be hooked into the code base, it's that type of repetition that helps teach the pattern rather than summarise the options.
Awesome Explanations and fluent demonstrations on Request-Response Pipeline for Nest JS . I really appreciate your efforts and thank you very much for such deep insights !!
hi, this is a beautiful tutorial. Thank you!!! But i have a question, why in the interceptor, the next.handle() return an observable? i am expect something like: const result = next.handle(); // do something with result return result; Thank you!
Thanks for the great video. But I have one clarification: we can still use global interceptors in main.ts Example: app.useGlobalInterceptors(new LoggingInterceptor(await app.resolve(RequestService)))
Thanks for the explanation. It's quite clear to understand the differences between Middleware, Pipes, and Interceptors 👏. There is a catch though. You are injecting "scope Request" like Santa is giving candies 😃. But this has huge side effects. For example, in the user service, it means that the app will have a new instance of the service for each request and moreover, a new instance of every class this service is injected into. This will massively slow down the app. And same for the LoggingInterceptor: each request = a new instance of the logging class → memory-intensive. How can we overcome that? What would you recommend as an alternative to your current solution?
Hi thanks - and great question as this is a valid concern. I recommend using Node AsyncLocalStorage. You can find other packages wrapping it like this one: www.npmjs.com/package/nestjs-request-context
Could you tell me where would it be best to place business logic in nest app? The example of such business logic is checking if resource that is about to be created has a unique name, however the name uniqueness is scoped to some information inside request object (i use passportjs which ends up attaching decoded jwt content in the request object), or e.g. checking if referenced resource exists when updating - then id of the resource is one of the URL params and update data is the body? I cannot find anything in the docs that will fit my needs. Please help
Can you also do tutorial on nestjs prisma using pg db to do cascading delete, soft delete, and many more logical concept or ideas? Can you also update or making new series on socket io backend server using nestjs prisma orm as use of pg db? Thank you for this tutorial🙏🏽
Hi @Michael, Does this order change at all if an exception is thrown by something before the route handler? Ie, I was getting a 413: RequestPayloadTooLarge, which I think is an error from Express, and my global ExceptionFilter was being triggered but not my interceptor. If the error occurs anywhere inside the actual method, then the order happens as I'd expect from this video. Thanks
does a middleware or an interceptor can be used to check if incoming request has some value in header, like accept-version, or token etc (without checking the content of the value) ?
Hi Michael - thanks for the great video! Have you tried out v10 of nestjs graphql? Its plug-in based now and supports Mercurius and as of v10.0.6 is supports federated subscriptions which would be cool to see.
just putting it out there, but was anyone else ready to smash their keyboard at the wildcard route not working for the middleware? i tried every which way bloody regex combination and in the end, an empty string worked. i hate my life. Nest v10.1.0 in an nrwl/nx monorepo for reference....
Brother. A quick help pls Nestjs and mongoose. Nx monorepo I have organisation module, product module and category module. - product schema defined in product module. - category schema is defined in category module. - organisation schema defined in organisation module. But schema has a array of products and category as subcollection to org collection. - when I create a product or category, I need to use organisation model in product and category module. So i would need to import organisation module in product and category module - since I have product and category as subcollection to organisation schema. I need both product and category imported in organisation too. This makes it circular dependent. How to approach this use case. Plz help.
Get my highly-rated Udemy courses at a discount here: michaelguay.dev/udemy/
Hey Michael, I followed your tutorial on nest js microservice using RabbitMQ, but I did not find if you used service registry. My idea is to have an auth microservice and an Api gateway app listing on 3200 that essentially work as a proxy forwarding request to auth. I looked online, most of them were too complexes. Can you help?
Wow this was amazing! Thanks so much for teaching us all of this again! As always lots of knowledge gained from watching your videos. Many thanks! What I learned is that the path a request goes through in order is...
1) Middleware - For things like authenticating a user
2) Guards - To check a user is authenticated before getting to the controller (manager of the task) among other use cases
3) Interceptor (before) - Can be used to log the method, url, userAgent, ip, controller name (ie., AppController), controller handler/method name (ie., getHello). Can also be used to transform incoming data
4) Pipes - Can be used to freeze parameters in the request so it isn't mistakenly changed in the code. Also validate input data, transform input data, etc. Typical usage is validating request parameters with built in NestJS pipes like ParseIntPipe, ParseArrayPipe, ParseUUIDPipe
5) Route handler - The "manager" that tells the provider (ie., service/worker/task implementer) what to do
6) Interceptor (after) - Can get the response and status code after handled by the control handler (ie., the method/function inside the manager). Useful for logging. Can be accessed via next.handle().pipe(tap(res=>{}))
7) Exception filters - To log errors internally or change the error response into user friendly wording for better UI
Then it becomes a beautiful response
Wooh! Just wrote the above to summarize what I learned - all info from going through this video. Thanks again and looking forward to your future videos! And ofc I gave your video a like as it's very helpful.
Thank you! And that is a great textual summary.
One of the best explanations I have seen. In just 30 minutes every things is explained in such a depth.
I've been using NestJs for 2 years and wirh this video I have witnessed the power of scoped dependency injection. Thank you!
this is so great, been trying to figure out how I'm gonna get all the userIds to track operations and permissions. Gonna watch this properly next week and refactor my code.
This is a useful example to quickly understand the concepts of NestJs. I had forgotten all of it as I didn't use it for few months. Now trying to quickly revise the concepts and also understand other things which I had not used before. Your videos have been very helpful!
Best diagram to get an overview of what is used when
I just got some lessons on good architecture here :)
The request service and freezing requests, am definitely applying that onto my current toy project and beyond.
Thanks a lot Michael
Great video, you deserve many more subscribers, keep up the great work.
I love it that you take the time to keep going through the different ways that features can be hooked into the code base, it's that type of repetition that helps teach the pattern rather than summarise the options.
Thank you very much!
One of the best explanations I have seen. Thank you so much for the great video Michael.
Thank you!! what a nice and clean way to explain how nest works
This is a great video, I wanna say thank you for explaining these concepts in an easy way
All of this stuf were explained simple and clear... Thank you!
Awesome Explanations and fluent demonstrations on Request-Response Pipeline for Nest JS . I really appreciate your efforts and thank you very much for such deep insights !!
Concept simply explained. You deserve more subscriptions. Thank you very much!
This video is very useful. The nestjs framework is huge. It is similar the complexity like Laravel in php language.
thanks so much for this video it helped me alot understanding the response request path and how to implement it correctly
Super explanation about the framework flow architecture, Really a great job.
my brain melt down when i saw that request provider scoop exists 🤯🤯🤯
Very well! explained clearly now I can move on :))
thank you this sharing amezing video and keep it to help my codding careet
Thank you so match,All love.❤
wow, OMG, sec by sec was useful for me. thank you.
This is amazing! Thanks Michael
Awesome please keep posting videos like these!
Nice walk through
Thank you Michael !!! You are The best🤩🤩
Very nice tuto. Good exemples, it helps !
hi, this is a beautiful tutorial. Thank you!!!
But i have a question, why in the interceptor, the next.handle() return an observable? i am expect something like:
const result = next.handle();
// do something with result
return result;
Thank you!
Thanks for the great video.
But I have one clarification: we can still use global interceptors in main.ts
Example:
app.useGlobalInterceptors(new LoggingInterceptor(await app.resolve(RequestService)))
this is awesome , i hope you will post video like this in future
Thanks for the explanation. It's quite clear to understand the differences between Middleware, Pipes, and Interceptors 👏.
There is a catch though. You are injecting "scope Request" like Santa is giving candies 😃.
But this has huge side effects. For example, in the user service, it means that the app will have a new instance of the service for each request and moreover, a new instance of every class this service is injected into. This will massively slow down the app. And same for the LoggingInterceptor: each request = a new instance of the logging class → memory-intensive.
How can we overcome that? What would you recommend as an alternative to your current solution?
Hi thanks - and great question as this is a valid concern.
I recommend using Node AsyncLocalStorage. You can find other packages wrapping it like this one: www.npmjs.com/package/nestjs-request-context
Greate tutoria please create more video about the full authentication process and authorization with JWT, thank
Thanks a lot!
Everything worked fine !
Thanks a lot for the video!
Could you tell me where would it be best to place business logic in nest app? The example of such business logic is checking if resource that is about to be created has a unique name, however the name uniqueness is scoped to some information inside request object (i use passportjs which ends up attaching decoded jwt content in the request object), or e.g. checking if referenced resource exists when updating - then id of the resource is one of the URL params and update data is the body? I cannot find anything in the docs that will fit my needs. Please help
As we say in my country, you left 10 fields... Congratulations, your content is too good :)
Y'all ok over there?
Can you also do tutorial on nestjs prisma using pg db to do cascading delete, soft delete, and many more logical concept or ideas?
Can you also update or making new series on socket io backend server using nestjs prisma orm as use of pg db?
Thank you for this tutorial🙏🏽
A Prisma video is in the works.
Hi @Michael, Does this order change at all if an exception is thrown by something before the route handler?
Ie, I was getting a 413: RequestPayloadTooLarge, which I think is an error from Express, and my global ExceptionFilter was being triggered but not my interceptor.
If the error occurs anywhere inside the actual method, then the order happens as I'd expect from this video.
Thanks
A.M.A.Z.I.N.G (truly)!
You are amazing man.
Wow awesome video. Thank you.
Can u explain please why we need to set scope as request? Cuz thats not so clear in this case
Awesome Awesome Awesome Awesome Awesome
Thank you for the video !
Very nice! Thx! 👍
Can you make videos on configuration, caching and task scheduling on nest js? Also websokets are appretiated.
Great work thanks
Sir how can stored the logging information with http response in file?
for some reason the method getUserId of request service returns undefined in other controllers than app
does a middleware or an interceptor can be used to check if incoming request has some value in header, like accept-version, or token etc (without checking the content of the value) ?
Yes! This is a great place to make that check.
Nice explanation but `Guards` are supposed to be used for Authentication and Authorization as long as I know in Nestjs app
AWESOME!!!
Thank you ❤
Hi Michael - thanks for the great video!
Have you tried out v10 of nestjs graphql? Its plug-in based now and supports Mercurius and as of v10.0.6 is supports federated subscriptions which would be cool to see.
Thank you! I played around with it briefly, but I will have to take a closer look into federated subs.
How do you inject the request service in other modules? Does not work for me.
Same here! It only works in App Module
just putting it out there, but was anyone else ready to smash their keyboard at the wildcard route not working for the middleware? i tried every which way bloody regex combination and in the end, an empty string worked. i hate my life. Nest v10.1.0 in an nrwl/nx monorepo for reference....
Very good explanation. I couldn't have done better :)
Brother. A quick help pls
Nestjs and mongoose. Nx monorepo
I have organisation module, product module and category module.
- product schema defined in product module.
- category schema is defined in category module.
- organisation schema defined in organisation module. But schema has a array of products and category as subcollection to org collection.
- when I create a product or category, I need to use organisation model in product and category module. So i would need to import organisation module in product and category module
- since I have product and category as subcollection to organisation schema. I need both product and category imported in organisation too.
This makes it circular dependent. How to approach this use case. Plz help.
Prisma is gonna be the end of Mongoose.
thank you! and subbed!
the best
I dont get it :'(
How long you learn nestjs until you can understand that diagram?
Try looking up some example use cases online and then try to implement for yourself in a side project.
thanks man I really need this ..
my question is simple : WHERE DO U GET ALL THIS KNOWLEDGE LOLLL (btw thank you soo much for the video !!)
this guy is so pretty