Was looking for this video and absolutely loved it. Would suggest to upload more NodeJS advanced concepts and it's helpful to me and others and your explanation style is really good and find it easy to understand. Keep up your good work 👍😃
Awesome video, lots of stuff I didn't know. I think, if you're charitable enough with TCP, it does follow a bit the principle of streams. TCP doesn't wait for a response for each packet, it uses a "window" of packets (maybe it's similar to HTTP/2? not sure). Over time, they even added an extension to make that window bigger. But as networks get faster and faster, the window has to be bigger.
This is such a good video. thank you! Could you direct me to any resource that discuses rabbitmq in the context of a node.js app which is using the cluster module. trying to avoid multiple connections and wondering how connection pooling would work there.
Ohh this is great: new sbscriber ☺️..! I am working on a project where the goal is to build a service that allows to make a deep learning pipeline from scratch(features extraction, training, deploylment). your video was helpfull. Thanks.
Thanks a lot for awesome tutorial. Got a bit confused about the synchronous and asynchronous explained around 2:07:00, what do we mean by saying Snchronous means, you make a request and wait for the response, but still you can do other things?? Isn't this asynchronous??? And the reverse as, for Asynchronous you hit a service , you immediately get a response, it's just that the HIT doesn't need to be at that moment itself, it can be queued...but once you hit the service, you get the response immediately in async?? Didn't get this, why does it needs to be immediate? I though it's more of like promise, where to hit some other service, do your other stuff, and once you receive the response, you process it. Can you please share some thoughts?
I hit the like, even before completing the video xD Btw, Hussein, can you kindly create a "Discord" channel ?? it will be easier for us to get in touch and communicate, help .. etc
At 1:0:00 code starts, interesting...! At 2:30:18 Why some orders are processed on fast pace... remember the PRIORITY QUEUE everywhere for PREMIUM MEMBERS..:D
Hello, I would like to ask if it is a good practice to have a message consumer in frontend web app? I suppose no, because in this way the rabbitmq server's credentials could be seen by everyone and so anyone could consume your information as well, right?
Nice one..what can I say..aa yes "GOLDMINE" would be perfect. One more thing... can you please just put a list of the books that you have right back on your book shelf.... heheheehehe
Hey Hussein, are you learning French? You sound awesome when you utter french in between the video. Anyhow, I really love the way you present the content. Just, no need to put efforts to comprehend it, goes and sits in the deepest parts of mind in the first go. Love ya.
Obviously you missed the whole point with AMQP/RabbitMQ. The way you use RabbitMQ don't justify the intended use of AMQP and RabbitMQ. You should just use zeroMQ or Redis. If you want to explore a technology, don't just do a hello world example. Try to understand what AMQP is and what it was designed for. As you said in the beginning. "Everything developed has a purpose" a business case to solved. You example is NOT that business case.
![[Full] 4 ต่อ 4 Celebrity EP.910 | 22 ก.ย. 67 | one31](http://i.ytimg.com/vi/4TR3MVpOiw8/mqdefault.jpg)
I'm commenting ahead of time just to say thank you for your time and knowledge. I've been excited for a course like this from you.
I appreciate that! much love
Nice! Was going to suggest an RMQ live stream. This is a great compelation. Love any advanced RMQ content Hussein. Sharing with the team.
Glad it helped !! Thanks for sharing
Was looking for this video and absolutely loved it. Would suggest to upload more NodeJS advanced concepts and it's helpful to me and others and your explanation style is really good and find it easy to understand. Keep up your good work 👍😃
Love how this guy explains! Such an awesome guy you're Hussein. 🔥🙏
Awesome video, lots of stuff I didn't know. I think, if you're charitable enough with TCP, it does follow a bit the principle of streams. TCP doesn't wait for a response for each packet, it uses a "window" of packets (maybe it's similar to HTTP/2? not sure). Over time, they even added an extension to make that window bigger. But as networks get faster and faster, the window has to be bigger.
the Gary Vee reference though 😂😂😂 Thank you for your amazing content
Thanks a ton Hussain. Its always a pleasure to learn stuff from this channel.
Man I just love your energy and thanks for covering this topic 👍
Appreciate it!
topic or queue? :p (pun intended)
Thank you for this in-depth explanation.
Machallah, great content as usual 💪❤❤
Amazing man !! Great & useful work 🎉
Hello again my Hussein, thanks for vids!
Hi can you make a video on NATS streaming server comparing it with kafka and rabbitmq?
This is such a good video. thank you! Could you direct me to any resource that discuses rabbitmq in the context of a node.js app which is using the cluster module. trying to avoid multiple connections and wondering how connection pooling would work there.
Ohh this is great: new sbscriber ☺️..! I am working on a project where the goal is to build a service that allows to make a deep learning pipeline from scratch(features extraction, training, deploylment). your video was helpfull. Thanks.
Thanks a lot for awesome tutorial. Got a bit confused about the synchronous and asynchronous explained around 2:07:00, what do we mean by saying Snchronous means, you make a request and wait for the response, but still you can do other things?? Isn't this asynchronous???
And the reverse as, for Asynchronous you hit a service , you immediately get a response, it's just that the HIT doesn't need to be at that moment itself, it can be queued...but once you hit the service, you get the response immediately in async?? Didn't get this, why does it needs to be immediate? I though it's more of like promise, where to hit some other service, do your other stuff, and once you receive the response, you process it.
Can you please share some thoughts?
Its an important concept that I explain here th-cam.com/video/N5Ky-mz6n-8/w-d-xo.html
dude. You are amazing. Big shot out
I hit the like, even before completing the video xD
Btw, Hussein, can you kindly create a "Discord" channel ?? it will be easier for us to get in touch and communicate, help .. etc
i hit the like before even start the video lol
At 1:0:00 code starts, interesting...! At 2:30:18 Why some orders are processed on fast pace... remember the PRIORITY QUEUE everywhere for PREMIUM MEMBERS..:D
Thank you for this!
awesome. thank you
You bet!
Thank you so much for the video...
FREAKING AMAZING
Hello, I would like to ask if it is a good practice to have a message consumer in frontend web app?
I suppose no, because in this way the rabbitmq server's credentials could be seen by everyone and so anyone could consume your information as well, right?
Nice one..what can I say..aa yes "GOLDMINE" would be perfect.
One more thing... can you please just put a list of the books that you have right back on your book shelf.... heheheehehe
Hey Hussein, are you learning French?
You sound awesome when you utter french in between the video.
Anyhow, I really love the way you present the content.
Just, no need to put efforts to comprehend it, goes and sits in the deepest parts of mind in the first go.
Love ya.
How client will know packet didn't receive at server using stream(UDP) ?
Great video. Thanks a lot
Glad you liked it!
Thank you so much 🔥
WOW! Thanks!
ممتاز
بارك الله فيك.
Hello Wisconsin!
Is AMQPS better than WebSTOMP? Love the Gary V joke haha
253 Quigley Mountain
Super
Lol "why am I referring to computers with gender.." cracked me up
Here is the link to the article: doordash.engineering/2020/09/03/eliminating-task-processing-outages-with-kafka/
thanks! updated the description as well
It's the best thing ever!! (not really) LMAO
1:18:44
29:34 LOL
comment 1
The publisher should not know about the queue but only the exchange! That is the goal of AMQP...
you should keep your volume steady, too much dynamic in your audio makes me tired of listening even your content is great
i’m having a man crush
Obviously you missed the whole point with AMQP/RabbitMQ. The way you use RabbitMQ don't justify the intended use of AMQP and RabbitMQ. You should just use zeroMQ or Redis. If you want to explore a technology, don't just do a hello world example. Try to understand what AMQP is and what it was designed for. As you said in the beginning. "Everything developed has a purpose" a business case to solved. You example is NOT that business case.
comment 1