Microservices and Message Queues - Explained

It's time to take a closer look at Microservices and Message Queueing to uncover the benefits of this architecture.

We will use an application where users can upload and rank each other's photos as an example. In the first version everything is built into a single system, with highly coupled functionality. This is often referred to as a monolithic application. And as we will learn, this approach has many downsides. Especially when it comes to performance, reliability, scaling, and maintenance.

A much better architecture is to divide the functionality of the app into separate microservices. And in order for this to work, we need to use a Message Queue as a broker. The Message Queue will manage all communication between the different services. Some of the benefits mentioned today are:

- A micro service architecture makes your application highly scalable.
- Low coupling between parts leads to easier development and maintenance.
- The different micro services can be written in different languages
- Fault isolation is achieved. The app is still accessible even if one part of the system is down temporarily.

Segments:
Introduction: (0:00)
Monolith Architecture: (0:37)
Microservice Architecture: (1:24)
Message Queue as a Broker: (2:00)
Benefits of a Microservice Architecture: (2:51)
Summary: (4:21)
Outro: (5:07)

New to RabbitMQ? What is RabbitMQ?

[yuvaraj]

Beautiful explanation whatever mentioned has been done in a crystal clear manner. Thank you

[javaprogrammingmastery]

I am building my final year(BSc in CSE) e-commerce project using spring boot based on microservice architecture.

[Djw]

Great video! Using a high level example is very helpful.

[Drampam]

One of the best explanation! And I watched a lot!

[sabbaticalcountdown]

Amazing explanation and very straightforward; thank you!

[adnangulegulzar]

I was trying to build a message queue when I started focusing on how her smile is like Katie Holmes from Batman Begins. Stay focused my fellow men and women.

[omarimai]

subscribed from the first video, very good explanation :) !

[sumarouno]

Nice explanation about micro svc. The msg queue need more explanation, new video would be great. Thanks!

[ErickDavidD]

El mejor video que he visto de microservicios y colas, excelente, esa chica es guapa

[renepardon]

Would you prefer using gRPC and let the frontend call individual services or building an API gateway? There is a lot of pros/cons on both solutions. I like more the Idea of control and API gateway.

[mks]

I like ur smile, while talking with smiling so good.final summary is nice

[hasithasubhashana]

Aaand nice explanation with a real world scenario. Thank you

[tilik]

Is this the case for another 'naive microservice' example: all of the services depend on each other when forming valid business transactions. In other words, we still have a monolithic app broken down on modules, but instead of relying on API we introduce a messaging layer, which is not needed for the monolithic app. Where am I wrong?

[vishalsingla]

How would you recommend handling a scenario lets say you have an Active-Passive cluster where you want to ensure that only one cluster is processing the messages from the queue which is shared b/w the two clusters?

[martinabeita]

although the video is about message queue, can i use gRPC instead of message queue for the abbbove example? if yes/not then why?

[isanrodrigueztrimino]

Sounds like a lot of work and complexity for something simple...