RabbitMQ Core Concepts: Brokers, Exchanges, Queues & Routing Explained

[Music] Hey hello everyone welcome to a new video in this second rabbitmq dedicated video we continue our momentum after the introduction don't hesitate to

subscribe so you don't miss the next rabbitmq dedicated videos and to the channel don't hesitate don't click on join if you want to support the channel by the hans and around you put blue shoots etc so

the objective today is to discover the main definitions which bring concepts to the level of rabbitmq so to start we so going to come back to the basic principle of rap i thank you we have a producer a tail

and consuls mood we'll see that it's a little bit more complex of course than that with things that are a little more accomplished which allow jitter to manage different scenarios we will see that later so first

important definition the product comes out so we saw it we talked about it during the previous video its objective what is it to create me ssages and to push them in these famous that even if it is a little more complex than that

in any case to push its towards the rabbitmq servers the objective of this sister product it will be to format these following messages a given format it doesn't matter it's going to be full text thyssen or other it's going so

happens sister will generally use unilabs is a library therefore which will allow it to simplify its connection mode high to what are called brokers or rabbitmq servers with different types of

possible language python java php etc its purpose is therefore to send a message due to constitute a message and to send it in this queue with a secure mode in particular with a couple user password and possibly we have seen it during the

previous video possibly with simply Versailles security via certificate then the other important definition is what is called a broker so in the dough instead of those of yesterday so on the one hand we have

produced tonight on the other side we designed mores and in the middle we have our famous broker we have the same the same definition as for kafka finally what is it one of the servers who will carry beat 'em ku who can be

possibly in cluster mode so the stories and and which will host the queues in question so that's something that is important behind also comes from the notions of security and partitioning which are important what

we will see in particular with the greens is in a definition a little further, the objective being therefore for its servers to be able to create forms of isolation within its own instances

behind we have what we have therefore consumes hours consumes them hours of which classified they will seek to subscribe to one only to consume the messages and there again with different libraries in different languages ​​too but we have seen it

with the protocol at mqp we have the possibility of having sister products in a language and consuls in a different mood in another language messages few things to say they are of different types and therefore a little s they are

different types therefore of different content and we will be able to have lieder there also a typo is therefore to encompass all that metadata knows that it will also allow therefore to be able to consume these

messages the routes and we will see it is a little later and behind these messages are ordered to be able to be consumed in a given order they can be replicated or not possibly replicated according to the case

to the letter of mirroring or not then behind so suddenly if we go back to the main roles so finally we have the producers the broker where the brokers and consumes it hours in fine is then if we focus we

open a little more on the broker what kind of channel do we have in this broker first entry point at the broker level is the channel the channel what is it really the connection entry point for clients

so sister products and its objective it's going to be what's going to be multiple excess connections and to manage the connection itself so if we take a piece of code for example here angot well we're going to create a

connection from those from chanel in order to then be able to subsequently publish messages behind we have we follow up with a second element which is central to it is very very important at the level of

rabbitmq it's what we call exchanges it's exact challenge their objective c what are they responsible for receiving messages so there just after the connection so the mule which multiplexes

the connection we therefore have this connection which establishes and therefore we need to process messages and receive its messages it is the entry point they are different types and four main types the direct the fans out the

topics is leader we will see that a little later and we will see that in each case we have different possible behaviors in the line ement of messages and in the routing in particular messages

always at the level of the lighting we therefore have a sub-part which we call the binding so we are always in the broker in the chase we have this binding this binding what is it it's the link between a data exchange and a queue so we

can have several links with an exchange is different than that it's quite possible and so it's a kind of connection finally between this exchange team which is the point entry just after the channel to a

what to give and we go so it's a little bit different from the routine that conveys just after because it's not at the level of messages like the routine that the goal is going to be to really create a connection and to say its texture

disconnected to such and such that with possibly which is characteristics given behind so as I always told you therefore in the challengers we passed therefore the binding so this assembly between

the challenges is there that behind we have this q we call a routine which therefore the routine which is is located at the level of the messages it is an element which is deposited at the level of the message in particular at the level of the sister product and which will allow to

route and following given rules therefore following elements that are contained at the level of the messages of power route and its messages in such and such that with behaviors gave therefore suddenly it is good to take into account is

coupled therefore to the type of exchange in question therefore when we will see the types of exchange it is necessary to realize that there are types of exchange and at the same time we will apply or not a routine which will allow to have

quite successful behaviors behind of course we have the queue so that we would not have talked about but so far but here we are unfolding things a little bit anyway we briefly talked about its purpose what is it to store

messages possibly to have beyond replication we have different types of that therefore we have the classic We have the kg quorums where we were going to stream so we 'll see that a little later with char ding possible with stream

mode stream a little bit to come back to a kafka method and it's durability also very important since it will allow us to keep or not the that in case of restart of the famous broker

levet is so we haven't talked about it too much so far it is located there at the level of the broker from a general point of view, that is to say that the broker provides a rabbitmq instance but within this instance rapid m which we will be able to create

different different sub instances finally different instances within rabbitmq itself to be able to create a separation an isolation a little bit how to find the swift and au

apache level but we can consider a little bit the same thing, that is to say that we have a process rabbitmq data is behind for each of them for this process we will decline it with different sub-entities which are these

famous host worms who von t allow to create a real isolation of the resources of the characteristics of all the elements which are contained in this ver us with users it will be as soon as

exchanges etc so that it is valid both on a single broker but also when we are in cluster mode on all the brokers so if we take the path we had at the very beginning finally there is a little

more successful we have producers who will manage their connection with multiplexing via china one to a chain and behind it we will connect to an exchange with this ex young so suddenly this one is bandaged

on one that gave so it's the famous binding and then our messages according to what they contain well we will be able to routes and therefore depending on these two parameters or not within a taking into account of a

routine which follows therefore suddenly our messages arrive in a tank and the subscription of consumers 7 that allows the consumption of this hen here is therefore I am father that you liked this video do not hesitate to share to put

blue shoots commented to click on join to support the channel and I tell you see you very soon on def