Wonderful video, awesome content. Looks like inbuilt socket. You content is super unique, indepth, hardly youtube videos on this. Lovee it keep posting. Next video idea, how about explaining unknown many inbuilt features of nodejs which are native in like like events, URL constructor etc.
Great content, in meanwhile you spoke about handling these events in different services. It's about don't wasting time in the publisher service right ? How you do that ? with cluster module or something else ?
Hey, good question. The cluster mode is about scaling, while event emitters are in the realm of the "event-driven architecture". So if you want to free up the publisher service, the event-driven approach is the one you need. If despite that, the service is under high pressure, then scaling out with Kubernetes (if it's a microservices architecture) or simply the cluster mode of Node.js can be a good idea.
Great video! First time I found a channel about advanced Nodejs topics so well explained!
Welcome aboard!
Brilliant videos. Your channel is a gold mine
Thanks so much!
Wonderful video, awesome content.
Looks like inbuilt socket.
You content is super unique, indepth, hardly youtube videos on this. Lovee it keep posting.
Next video idea, how about explaining unknown many inbuilt features of nodejs which are native in like like events, URL constructor etc.
Great content🤗 keep posting please
More to come!
Can you please make font bigger? Thank you!
Will do next time 😉
Thanks for the useful informations :). I missed the implementation of the class EventEmitter and his methods ;)
Master, do you have any course about topics like this and any other advanced topics about Node.js? Or can you suggest some that you consider valuable?
Great content, in meanwhile you spoke about handling these events in different services. It's about don't wasting time in the publisher service right ? How you do that ? with cluster module or something else ?
Hey, good question. The cluster mode is about scaling, while event emitters are in the realm of the "event-driven architecture". So if you want to free up the publisher service, the event-driven approach is the one you need. If despite that, the service is under high pressure, then scaling out with Kubernetes (if it's a microservices architecture) or simply the cluster mode of Node.js can be a good idea.
Awesome lessons.
great content just love it❤❤
Could you make a project video with testing and production stages. Thank you. 🙏
Can we make EventEmmiter queue, and execute all asynchronous methods in this queue, or this is bad idea?
I wouldn't do that, sounds like a bad idea :) I'd rather go for a robust queueing system / library if you require one
Good video!
thanks
Nice video bro. I might not have a brain, but i got an idea.
does it make the project more heavy ?
Not at all 🙂
thank you
Well I tried to like this video 2 times.
You have explain it very well. But for beginners it will be a little bit hard to absorb all the logic.