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)
CloudAMQP is the largest hosting provider of the open source message broker - RabbitMQ. Try it free - www.cloudamqp.com
New to RabbitMQ? What is RabbitMQ?
Our blog series "RabbitMQ for beginners" is the perfect introduction - www.cloudamqp.com/blog/2015-0...
Or download our popular and free RabbitMQ Ebook - www.cloudamqp.com/rabbitmq_eb...

[@Djw3999]

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

[@yuvaraj9268]

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

[@addliam]

The example make it easier to learn

[@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.

[@sabbaticalcountdown]

Amazing explanation and very straightforward; thank you!

[@ErickDavidD]

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

[@javaprogrammingmastery]

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

[@amirshahidi2973]

cute and good explanation

[@MrHav1k]

Beautifully explained!!

[@omarimai7428]

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

[@Drampam]

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

[@CloudAMQP]

Thank you!

[@eleandro]

@@CloudAMQP for me too

[@flashbangstudio9102]

Nice intro to message queuing

[@hasithasubhashana9606]

Aaand nice explanation with a real world scenario. Thank you

[@richardlanglois5183]

Great presentation!

[@cristianospina7858]

Excellent, thanks.

[@akshayarora891]

A very good explanation indeed

[@akshayleads]

Well explained! Thanks

[@madhurimamondal9756]

Thank you !

[@DJazium]

This is was very well explained!

[@vutuan7211]

Good explained! Thank alot

[@mks5988]

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

[@sumarouno]

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

[@CloudAMQP]

You got it! :) We will get to work right away. Stay tuned.

[@CloudAMQP]

Here is now a new video: czcams.com/video/5-Rq4-PZlew/video.html

[@AbhinavKumar-dr4ef]

Nice explanations.

[@renepardon7435]

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.

[@vishalsingla2004]

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?

[@ahmedhelal174]

Thank you

[@lewispil3529]

well explained !

[@tilik13]

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?

[@costagmc1]

beautiful...

[@guidyouguy7306]

Lovely

[@martinabeita8852]

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

[@1testrad]

thanks ...

[@isanrodrigueztrimino6701]

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

[@neillister9292]

Honestly, it mostly depends on what kind of business you are developing apps for as your solution/architecture should always consider things like scaling, load management, data persistence, etc. Even for developers that mostly work in small businesses, if you ever leave the company and interview somewhere else they will most likely want to see how you handle these types of scenarios.

[@shubhankarpaul2740]

She's so sweet man

[@evans8245]

sank yu sou much uh

[@hasithasubhashana9606]

omg you are cute.