What is a Message Queue?

Ойын-сауық

Learn more about Message Queues → ibm.biz/IBM_MQ_documentation
Check out IBM MQ → ibm.biz/product-ibm-mq
Check out IBM Cloud Pak for Integration → ibm.biz/prod-cloud-pak-integra...
A message queue is a component of messaging middleware solutions that enables independent applications and services to exchange information and are used across numerous deployment options, including optimized physical appliances, cloud services, mainframes, and as software.
In this lightboard video, Jamil Spain with IBM, visually breaks down and explains the different components of a message queuing solution architecture, different styles of message queuing, typical business use cases, and benefits provided to a developer.
Get started on IBM Cloud at no cost → ibm.biz/Bdfw4q
Subscribe to see more videos like this in the future → ibm.biz/subscribe-now
#MessageQueues #AsynchronousMessaging #Microservices

Пікірлер: 37

  • @__redacted__
    @__redacted__2 жыл бұрын

    This was one of the best explanations of message queues I've seen. Wondering when would an MQ be overkill? Would love to see a video on caching patterns.

  • @vishaljangid7638
    @vishaljangid76382 жыл бұрын

    14:10 I think we have come a long way, having java for frontend and javascript for backend :). Anyway, great video as always.

  • @samialesh7108
    @samialesh71088 ай бұрын

    This is one of the best explanations of message queues I've seen

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

    Extremely well-presented. IBM is a great source of content for these things.

  • @erikslorenz
    @erikslorenz2 жыл бұрын

    Excellent content! A very good example of a message queue is integrating systems. For example I have to bring orders over from an ecommerce system to our erp. But it rate limits me. So I let it chill in the message queue while the workers do thing

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

    Excelent video! I'm following the whole series

  • @glennedgar5057
    @glennedgar50572 жыл бұрын

    Great content. What I find useful is two data structures. One is a time based stream. This allows multiple consumers to access the single stream. The consumers access the stream based upon time stamps. The second is various summary tables for the stream. The asynchronous techniques which are mentioned above and i the video can be implemented on small systems or services using Redis

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

    How is this guy writing backwards so accurately

  • @MithrillPhoenix

    @MithrillPhoenix

    Жыл бұрын

    Reverted the stream)

  • @johnyepthomi892

    @johnyepthomi892

    Жыл бұрын

    It’s mirrored. IBM shared some details on it.

  • @elcapitan6126

    @elcapitan6126

    Жыл бұрын

    this is a pretty commonly used technique. you'll never see it live though :)

  • @kidpudel

    @kidpudel

    6 ай бұрын

    @@johnyepthomi892that’s a secret information

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

    Great content. Really helped to clear many of my assumptions. Thanks.

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

    I am learning distributed systems, and your video helps me a lot. Thank you for your effort. Keep going!

  • @updownftw_
    @updownftw_2 жыл бұрын

    This was the best explanation I’ve seen on MQuing

  • @omarsherif6198
    @omarsherif61982 жыл бұрын

    Great explanation sir

  • @TamLe-sh2ru
    @TamLe-sh2ru2 жыл бұрын

    Thanks. Great content!

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

    Very well explained

  • @Thinkingfeed
    @Thinkingfeed2 жыл бұрын

    Great content!

  • @dibri
    @dibri2 жыл бұрын

    message queues are architecture agnostic. still a great video.

  • @gorantodic1875
    @gorantodic18752 жыл бұрын

    Great video, fantastic, exactly how it should be!!

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

    great video

  • @DillionMegida-ow1gy
    @DillionMegida-ow1gy Жыл бұрын

    Simple to understand. Thank you for this!

  • @JuanHernandez-pf6yg
    @JuanHernandez-pf6yg2 ай бұрын

    Useful. Thank you.

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

    I have a service with a high response time the last few days. I tried inhibited put queue in mq explorer to reduce the response time, it turned out that there was a problem with another service. how do i solve it?

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

    Best explanation ever.

  • @chudchadanstud
    @chudchadanstud2 жыл бұрын

    subbed

  • @katzenschildkroete
    @katzenschildkroete2 жыл бұрын

    Jamil!!! Thanks!

  • @leftylooney3853
    @leftylooney38533 ай бұрын

    This is a way to chat with live stream videos?

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

    What are you writing on?

  • @IBMTechnology

    @IBMTechnology

    Жыл бұрын

    Search on "lightboard videos".

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

    Would this be the solution to my 30s + long request time

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

    Why would you EVER use message queue model instead of pub/sub? If a pub/sub can have MULTIPLE subscribers? Also could a message queue broker/bus like RabbitMQ CLONE the quote and give it to MULTIPLE consumers as well? You could keep a copy of the clone which gets stored as a 'log', if this situation is possible with message queue. To me a message queue does not even sound decoupled, at this point why don't we just write directly from app1 to app2 since there is only going to be one producer/consumer.

  • @BlackPriest96

    @BlackPriest96

    Жыл бұрын

    Because Pub/Sub is when you share the same data to different suscribers. Point 2 Point is when you have specific data to the consumer. Ex, you want to send orders to the customer, each customer has different orders (id, products, price) you cant send the same order to all customers that need an order. And Pub/sub example is when you have newsletter, and many customers are subscribed to your news letter. Hope it makes sense.

  • @BlackPriest96

    @BlackPriest96

    Жыл бұрын

    Another thing, you cant send information from app 1 to app2 directly as you said. Imagine you have an antifraud system, that delays like 1 minute to check if the order is fraud or not. Are you going to let the customer wait for 1 minute until the anti fraud system decides if it's fraud or not? Of Course not. The queue is going to send that information async, and wait the response asyncronous. Another example. Customer purchases something, emails normally takes like 10s or even more to be sent. Customer is not going to wait on the checkout until it's email is sent, it can be on a queue running on background.

  • @anamsajid06
    @anamsajid0611 ай бұрын

    Is he... writing mirrored?

  • @IBMTechnology

    @IBMTechnology

    11 ай бұрын

    See ibm.biz/write-backwards

Келесі