Want to learn more about these concepts and how to build production-grade Node.js Microservices? Check out my highly-rated course with this discount code: michaelguay.dev/udemy/
@johnisutsa16419 ай бұрын
I decided to take the time this month to really try and understand JS and its various runtimes like nodejs, and how it works. Then, this video comes up. Literally perfect timing. Thank you. Excellent teaching as always.
@ivanuskov8623 ай бұрын
Great video, really helped to understand core concepts of js and async code in js, thanks! wanted to mention that better to use Promise.allSettled instead of Promise.all allSettled handles a little differently (returns status and value) but doesnt stop if rejected promises occur
@cesargamer12319 ай бұрын
Insane, make more courses, yours explanations are soo good
@mguay9 ай бұрын
For sure, stay tuned. Thank you!
@nikhilgoyal0076 ай бұрын
My note: @13:00 how promise does not block it. (it is async sleep rather than being blocked)
@CookerSingh7 ай бұрын
A new fan is coming right away, please make more videos on scaling and building production level code logics and optimisation, cause no one is doing that except Copy Pasting 🎉❤ Request: please make a video on how to setup typescript for production react app.
@emreaka39659 ай бұрын
15:32 and C#. Even with async await syntax utilizses multiple threads. Thank you for the video.
@souhailDevv9 ай бұрын
This is gold, thanks a lot. Can we achieve multi threading by using a message broker/queue system instead of workers ?
@mguay9 ай бұрын
Still one thread, but we can scale horizontally by distributing the work to several applications - so it is very similar.
@mabad88926 ай бұрын
Thank you!! Very informative lecture and looking for further concepts.
@raymondmora71209 ай бұрын
Thanks Michael! Your content is amazing, i've learned a lot from you!
@Kady3DPrinting4 ай бұрын
Impressive
@gmg158 ай бұрын
Awesome content as always, One question though, if I have a limited knowledge on dockers and k8s, is it a good approach to go with node clusters instead??
@MightyKingKala9 ай бұрын
your content is a gem, thank you
@orchideirakozesr88429 ай бұрын
Excellent tutorial Michael , been following your channel for a while now . thought i'd throw in a couple of nuggets . I know for one that pm2 can be used to scale NodeJs processes , although K8s is a production grade solution it also requires quite a bit of an overhead , could we get alternatives ? I've also hear interesting stuff about Worker threads , maybe you could help us unpack that . Keep up the good work !
@mguay9 ай бұрын
I love the idea of a future video with PM2 and Worker Threads! Stay tuned.
@abolfazljalildoost7668 ай бұрын
Thanks for these useful videos. I love your tuts
@solomanter9 ай бұрын
Very helpful, Thanks!
@igboanugwocollins44529 ай бұрын
Thank you for this masterpiece
@hamza_dev9 ай бұрын
Wait. When we have I/O-bound tasks, aren't they passed to a thread pool and then executed on a separate thread by the kernel?
@mguay9 ай бұрын
Only for very specific tasks: DNS lookup, file-system I/O, Crypto & ZLIB The actual network I/O is completely async and handled by the kernel. Node (the event loop) simply moves onto other tasks while it awaits the response from the kernel stackoverflow.com/questions/51653440/does-node-js-use-libuv-thread-pool-for-network-i-o
@chris_ea8 күн бұрын
Brilliant
@mr.daniish9 ай бұрын
This content is so fresh and different that the cookie cutter dev content being produced out there! keep it coming Micheal
@stephanjames15369 ай бұрын
keep it up! you are doing a great JOB!!!
@outplays_39 ай бұрын
Hi @mguay, i wonder in this what theme are you using in vs code?
@belkocik9 ай бұрын
14:55 is there other way to write a non-blocking code? Rather than returning new Promise(), could I return just a function which contains a setTimeout inside?
@user-qm3sk8gv2q9 ай бұрын
Thanks for your amazing work !!👌🙂
@amirsaad86279 ай бұрын
Thank you Michael, And thank you for amazing Udemy micro-services neste course. It makes really big difference at my career 👍. Hope if there is more about could (Kubernetes, helm ) and how to manage clusters.
@mguay9 ай бұрын
For sure, stay tuned. Thank you!
@spikesolid6229 ай бұрын
Nice explanation
@mguay9 ай бұрын
Yes exactly, check out my video on Horizontal Pod Autoscaling to have this happen automatically based on CPU & Memory usage metrics!
@amirchegini90249 ай бұрын
Many thanks
@samatzhussipov11399 ай бұрын
Amazing Thanks!
@Alex-bc3xe7 ай бұрын
You are a really good developer maybe you should refine your branding and marketing strategy cause you have talent.
@mohammadrezabehzadfar81229 ай бұрын
Hi Michael thank for the nice video can you make a course for nestjs graphql microservice i mean even a paid course is fine i really want to know more about that
@mguay9 ай бұрын
Yes stay tuned for my next course :)
@dacam299 ай бұрын
Promise.all is concurrent, meaning they start executing in parallel, but, JavaScript being single-threaded, only one line of code is executed at a time (code inside callbacks)
@ofuochi9 ай бұрын
Node.js is designed for concurrent, not parallel, execution of operations, with a focus on non-blocking, event-driven tasks primarily suited for I/O-bound workloads
@khanumar69389 ай бұрын
now its capable of parallel excecution through worker nodes @@ofuochi
@GoYoops9 ай бұрын
Yea, and I think it's important to distinguish between the 2 terms for new developers that are learning instead of just deciding to use the term parallel when in fact all code execution is concurrent unless utilizing worker threads. The I/O network events can happen in parallel, but the actual code execution will always be concurrent.
@spikesolid6229 ай бұрын
Why can't we use pm2 for cluster mode?
@mguay9 ай бұрын
Stay tuned for a video on it!
@bombrman19949 ай бұрын
I am using Nuxt atm
@pluraltest92429 ай бұрын
Why does the function non blocking need to be asynchronous? You are returning a promise and not awaiting for anything
@mguay9 ай бұрын
It doesn’t need to be since we’re already returning a Promise like you said