RabbitMQ Introduction: Message Broker Basics for Microservices

[Music] Hey hello everyone I hope you 're well welcome to a new series of videos we're going to be interested today and we're going to start this series dedicated to rabbitmq so do

n't hesitate to subscribe so you don't miss it the next videos of this playlist or other videos of the youtube channel well on the youssef youtube channel which has more than 1200 videos do not hesitate to click on join if they

wanted to support the channel put blue shoots speak - around you as do many people among you do not hesitate to share them on social networks then inhabited th turn what can be

said about rabbitmq important links already on the one hand it is an open source project and therefore who says open source project we can access auby nerves rabbitmq rabbitmq servers in particular on its github repository is also the site

where we will be able to find fairly extensive documentation on rabbitmq with a lot of example s also on different languages ​​then rabbitmq its language what is it due to erlang was therefore developed by the company ericsson

this language r language which can be common in the end but which is present in some teeth some tools and which is a language which is quite effective so we 're going to talk about rabbitmq what exactly is it so it's a message

broker or a message bus when we're going to say a bit like kafka even if they are different in their operating principle but roughly speaking it works a little bit on the same principle

it's what we call an oriented middleware but it's gees so that is to say a word more exactly why we call it an oriented middleware but it's all about simply because we start from a sister product, therefore from a

message producer, then we will send its messages in a message queue which takes on different aspects we talked about kafka earlier so it takes on a different aspect depending on what let's be sure rabbitmq or on

kafka we will eventually see the differences and then also therefore a consumer's who will come and take back these messages designed but these messages of this fight so that's the men's women's zoo

in the end so it's not a comic log like kafka just in two words so it's a queue of messages so what does that mean so in the case of a beat'em ku it's what we call a fifo a first in first out that is to

say that our sister product produces messages or is here in a given order a consumer's will come to take them at the other end and as and when who consumes them finally it deletes from the tail then rabbitmq

has a plugin that allows you to make the stream a semblance of assimilating to kafka nevertheless their principles are still conceptually quite different at the base that we will say so that is

something that is quite important kafka works for him rather so on what is called a locke committee that is to say we find 7 that messages emails and messages are potentially can remain indefinitely in this that on

the other hand what will move is one of 7 that is to say a witness a flag a kind of milestones that will advance over time as the hours consume these famous messages but that means

potentially we can go back in time and re-seat is this this milestone this flag so let's continue on rabbitmq so society created what not company but product created in 2007 and therefore with a company behind which is called rabbit

technology ltd so behind there are also other companies which this world in particular at the level of the cloud to provide support etc today but to at the time in any case in 2010 springsource therefore bought rabbit

technology and at the same time double rabbitmq finally behind a springsource race which is what there was less of which means that today we can consider a little bit when same rabbitmq as property of vmware

of employees that it is nevertheless something which is nevertheless guaranteed over time so it is part of pivotal software today and therefore by this means of vmware currently we is in version 3

9 13 to know that there are versions that there is an evolution of versions we will say a little major in the possibilities of rabbitmq in particular between the 3 sat and the a38 we will see that later but that there have been

developments that are significant that we will say in particular in the cloud mode behind so what will allow us this famous operation with a sister product a skew message and a designed but it will allow us to

operate from asynchronously that is to say that simon sister products produces the most messages in the queue but as os designed mores does not consume the messages remain available if my product would be word

consumes hours does not consume at the same speed at the same rate well finally there but that's what we will allow to stamp then certain given period of time since we will not be able to store the

elements indefinitely but it will allow to stamp or vice versa if I lose the producer and I even tried how far who to what my my message bus which has messages to process my consumer's to be able to continue

its work so we can clearly see the possibility of working to operate in asynchronous mode moreover rabbitmq therefore makes it possible to have a cluster mode or rather different types of cluster mode we will see that later with

potentially ring numbers and then another queuing system that has existed since version 3 8 so many libraries also that is the strength of rabbitmq libraries that are relatively simple and easy to

use in different languages ​​so we will find java, php, piton du go etc. we will really find a lot and we find it very often, that's why moreover that globally the buts these two horses

have exploded we will say in recent years in particular we find them at the heart of the architectures of micro services to facilitate communication between the different micro services so that is

also something very important we going to say that it is a tool that is comparable to a mode of communication as I have just told you, particularly in micro service systems, is to say that rather than having two services that

will talk to each other other in the evening in https pgrp mode it doesn't matter we're going to have this time so this message that between the two which will really allow us to manage the asynchronous nature and manage other aspects in

particular we were talking about cluster mode so high availability the other interest so it will be the ease of maintenance and to say that as I said earlier we will be able to cut a sister product cut

one consumes hours without completely losing the possibility of i question the queue so that's really a fairly important asset , moreover also its ease of scalability, that is to say that let's imagine

g1 consumes hours which produces a lot of messages which produces them in the queue and that a single consumer's does not allow to follow this rhythm what is going to happen so he consumes messages at his own pace he takes them

as and when I added a second consumer's what is going to happen there suits him take the messages also in the queue and finally as they will take them each in turn and that a message which

is recovered from the queue is no longer present in the tank finally we will have a scalability which will also be facilitated as a result we are going to have a load distribution that will also be better manageable and better

integrated by this aspect so it is really something that is quite practical is also therefore it allows better management of failures, that is to say that if I lose m ais designed die for as long as my sister products can

continue to continue to work and to store elements in the queue and vice versa so that is something that is also very very practical so we will also be able to suddenly

in this what to store elements of different types that's just a brief example but there really are a lot of things that can be stored of different forms of different interests and objectives that's something that

's very important that can be for example business data we can therefore come from plugins even directly sent for example emails whose tail in a rabbitmq tank and have something that will consume them

behind or conversely have tails that will be sent thanks in any case by going through this cure also lived in miu text messages for example we will want to proceed with text messages or for example we have a site we want to edit

invoices we know that editing invoices in pdf format no bah vo there it gave request a little bit of resources possibly we therefore need to buffer to have an asynchronous character suddenly compared to the

treatment of our consumer's which has the role of edith helped for example of the pdf is there that will manage makes it possible to manage buffering things a little bit to give consumers time to do things

at their own pace possibly managing time phases during the day we will be able, for example, let's imagine we have we have a peak during the day of requests for invoices but the rest of the day we do nothing and the

message will allow everything to be buffered to manage the peak of activity and finally to distribute the messages as time goes by and as it consumes hours will have time, especially in off-peak periods

as well, so two high schools are really busy, so that's something that's also important, we'll be able to pass instructions there, so from a service to our rvice command lines also from a for example

from a job which is a lure this kind of thing if you go to see the playlist dedicated to aargau event for example I made an example of docker images that were launched at from the nkr lives m kyodo what does the rabbitmq message say

simply contained a docker image and a command to execute so images launched here is what I am describing precisely where jobs simply more generally to be carried out for trial it is things

also what can we say lives m kg or the other force of rabbitmq knows that he is able to support different protocols knowing that quite commonly we rather use the protocol has occupied so advanced message

that wing protocol him what is his interest is that if we have a producer who is on a given language and a consumer's on another language it does not worry him that we have a protocol which really allows to have to be

universal and to have completely to be completely agnostic with respect to the language all that is a fairly significant force the st to the mst ump sorry the text stream orient ty but it's protocol so it

works under tcpc a protocol which is a little less common we have another protocol which is quite quite commonly used for him the cooked m was therefore messaging telemetry

carries him his big asset is that he is very light in operation people so we really live on the tails and we will find him especially in haiti by example of the fact that it is light it will make it possible to

recover telemetry information on sensors possibly this kind of thing and to store it in the queue so that it can then be refined , the treaties etc and then also from the http so of course a protocol very

common so here we are not going to go back on it it is also possible therefore to manage security through then not only encryption but through encryption we will be able to manage security with certificates of

course where is also going to be able to add security we will see it later with the creation of users and the management of the perimeters and the rights of each of its users behind rabbitmq we will not detail its

plugins but rabbitmq forgiveness makes it possible to manage evidence of plugins plugins both body so that is to say managed by the project itself is validated and then plugins from the community therefore the most heterogeneous so

we will we will find different plugins in particular prometheus for metrics for example and then so that will be the subject of the next video we are going to have different notions different definitions and there it is quite important

to have them in mind to know a little bit what we are talking about at each times we will see different notions such as brokers exchanges ku binding routing and routine who and then what does a consume hours after 10 a.m.

and still other elements so here I hope e that you liked this video don't hesitate to share it give lice players and especially to subscribe so as not to miss the next videos click on join if they

wanted to support the channel and I'll tell you see you very soon on Joseph who bye