11 ) What is Message Queue | RabbitMQ | Kafka | System design basics

1) Why we need message queue
2) What is message queue
3) Working of RabbitMQ
4) Working apache Kafka
How to Scale Database : • 5) How to Scale the Da...
What is CDN and How it works : • 15) What is CDN and Ho...
System Design Basic Playlist : • Playlist

Пікірлер: 37

  • @DurgaShiva7574
    @DurgaShiva757410 ай бұрын

    Best explanation I have came across after going through approximately 10other kakfa videos 🎉🎉😊

  • @vkscoding

    @vkscoding

    10 ай бұрын

    Thank you so much 🙂

  • @jazzycoder
    @jazzycoder7 ай бұрын

    Magnificent explanation of queues, thank you very much!

  • @vkscoding

    @vkscoding

    7 ай бұрын

    Glad you enjoyed it! You can help this channel by sharing videos on social media !

  • @audiobooks97
    @audiobooks97 Жыл бұрын

    Really nice comparison of rabbitMQ and Kafka at the end, one could easily remembers that rabbitMQ push based to rmb all it's mechanism and benefits.

  • @vkscoding

    @vkscoding

    Жыл бұрын

    Glad you liked it !

  • @rifatislamrakesh
    @rifatislamrakesh Жыл бұрын

    Explained very well. Thank you!

  • @vkscoding

    @vkscoding

    Жыл бұрын

    Glad you liked it !

  • @abhishekgowlikar
    @abhishekgowlikar6 ай бұрын

    Nice explanation though basic but good for newbies

  • @razorr1920
    @razorr1920 Жыл бұрын

    Awesome content and great explanation. I was searching for an IOT back end architecture and landed on your video. I would be great if you could do a series on IOT track and trace back end and any simple application like current position and geofencing.

  • @vkscoding

    @vkscoding

    Жыл бұрын

    Thankyou so much for appreciating the effort. Input Noted for starting series on IOT

  • @razorr1920

    @razorr1920

    Жыл бұрын

    @@vkscoding there are many videos on Google iot, IBM Watson, Cisco and AWS IoT, but hardly anything where solutions are independent of such platforms. I haven't seen content where Middleware is explained. Like the reverse proxy for incoming connections, traffic load balancing, chached database for live updates of the IoT and final permanent storage/ database for reports retrival. The interconnect between these services and other microservice deployment for redundancy and their interconnections. I am a flight engineer by profession but love technology and its applications. Just jamming with you for some cool stuff that would be worth sharing. Anyways subscribed and notifications added. Cool stuff here...😇😇

  • @PraveenKumar-ft2kr
    @PraveenKumar-ft2kr Жыл бұрын

    Great explanation. nice presentation. 👏

  • @vkscoding

    @vkscoding

    Жыл бұрын

    Glad you liked it!

  • @dushyantchaudhry4654
    @dushyantchaudhry46545 ай бұрын

    Excellent

  • @suman_achary
    @suman_achary10 ай бұрын

    Great explanation

  • @vkscoding

    @vkscoding

    10 ай бұрын

    Glad it was helpful!

  • @yogeshpathak
    @yogeshpathak7 ай бұрын

    really best explanation

  • @vkscoding

    @vkscoding

    7 ай бұрын

    Glad it was helpful!

  • @mukeshbagaria4089
    @mukeshbagaria408911 ай бұрын

    keep up good work .

  • @vkscoding

    @vkscoding

    11 ай бұрын

    Thank you so much for appreciating my effort !

  • @Ashwanth-jf3gp
    @Ashwanth-jf3gp9 ай бұрын

    Thank you.

  • @vkscoding

    @vkscoding

    9 ай бұрын

    Glad it was helpful !!

  • @azhar0406
    @azhar0406 Жыл бұрын

    Hi, If I want very low latency. What you will suggest RabbitMQ or Kafka? How many vcpu and ram is necessary for the broker?

  • @vkscoding

    @vkscoding

    Жыл бұрын

    Apache Kafka is best known for its high throughput whereas RabbitMQ is best suitable for low-latency message delivery and complex routing as well. Recommendations for Kafka : Kafka Broker Node: eight cores, 64 GB to128 GB of RAM, two or more 8-TB SAS/SSD disks, and a 10- Gige Nic . Minimum of three Kafka broker nodes Minimum of three nodes in your cluster, you can expect 225 MB/sec data transfer. If you need throughput of 50 MB and thousands of events per second Node : 1 or 2 nodes CPU : 8 or more cores per node, although more is better DISK : 6 or more disks per node (SSD or spinning) RAM : 2 GB memory per node Network card : 1 GB NICs If you need throughput of 100 MB and tens of thousands of events per second Node : 3 or 4 nodes CPU : 16 or more cores per node, although more is better DISK :6 or more disks per node (SSD or spinning) RAM : 2 GB of memory per node Network card : 1 GB NICs If you need throughput of 200 MB and hundreds of thousands of events per second Node : 5 to 7 nodes CPU : 24 or more cores per node (effective CPUs) DISK : 12 or more disks per node (SSD or spinning) RAM : 4 GB of memory per node Network Card : 10 GB NICs If you need throughput of 400 MB to 500 MB/sec and hundreds of thousands of events per second Node : 7 - 10 nodes CPU : 24 or more cores per node (effective CPUs) DISK :12 or more disks per node (SSD or spinning) RAM : 6 GB of memory per node Network Card : 10 GB NICs

  • @azhar0406

    @azhar0406

    Жыл бұрын

    @@vkscoding Thank you for your detailed response bro.

  • Жыл бұрын

    I have 2 questions about RabbitMQ: How to handle the case that some messages are consumed failed so many times, it would cause a bottleneck? How to automatically scale the consumers if there are so many messages in the queue? Could you please help me to clarify this?

  • @vkscoding

    @vkscoding

    Жыл бұрын

    1) How to handle the case that some messages are consumed failed so many times, it would cause a bottleneck? Ans : We have to configure maximum retry for messages and Once the retry exhausted then we have route these message to the dead letter queue. We must configure dead letter exchange and dead letter queue to deal with dead messages. (TTL Expired Messages , Message dropped from queue due to queue size limit. Messages retry failed.) 2) How to automatically scale the consumers if there are so many messages in the queue? Ans : We can subscribe multiple consumer to one queue and we can configure multiple queue to one exchange as well.

  • Жыл бұрын

    @@vkscoding But the queue size could be unpredictable, I dont know is there any way to scale the number of consumers automatically, by docker containers or something like that? Btw, thanks for you solution on first question.

  • @vkscoding

    @vkscoding

    Жыл бұрын

    Regarding Consumer auto scaling for RabbitMQ on Kubernetes you can try this blog ryanbaker.io/2019-10-07-scaling-rabbitmq-on-k8s/

  • Жыл бұрын

    @@vkscoding many thanks

  • @nishanth1828
    @nishanth18287 ай бұрын

    Wow

  • @vkscoding

    @vkscoding

    7 ай бұрын

    🙏

  • @amboojmittal2993
    @amboojmittal299310 ай бұрын

    Its good and how can I reach you for mentorship?

  • @vkscoding

    @vkscoding

    10 ай бұрын

    I am glad you liked it. You can Connect via email.

  • @arupde6320
    @arupde632011 ай бұрын

    be regular

  • @vkscoding

    @vkscoding

    11 ай бұрын

    Glad you liked the Video ! Content will be updated weekly Basis ! Will try to increase frequency :-)

Келесі