We have just defined what is a Kafka.
It is distributed by subscriber messaging system and in every published subscribe system, messages
should be stored somewhere.
And also publishers should be able to send to where those messages and the subscribers should be able
to read from somewhere those messages.
And in a Kafka, brokers are responsible for all those operations.
They store messages and they sell publishers and subscribers.
But publishers in a Kafka are gold producers.
They produce messages to Kafka brokers and subscribers in a picture, Kafka A consumers.
They consume messages from Kafka brokers.
And most interesting that at every single physical server of Utah, Sarah, you may run multiple Kafka
broadcasts and they will be completely independent and you are able to create even Kafka Gloucester
on a single computer.
This Kafka broadcast, again, its main responsibility is up following first receive messages from producers.
Second thought those messages and thought give ability for consumers to read those messages, that's
all.
And the Kafka broker simply stores messages in files on a hard drive.
And producers are able to append messages to those files and consumers are able to read from those files
that that simple.
Also, it is possible to have multiple producers and multiple consumers like on this diagram, and multiple
producers are able to simultaneously produce messages to Kafka broker and multiple consumers are able
to simultaneously read messages from Kafka Breuker.
And of course, messages may be produced and consumed asynchronously on different moments of time and
noticed that there was a single weak point on this diagram.
And it is Breuker.
If this Breuker fails, nobody will be able to sell producers and consumers this way.
Usually nobody runs a project like that with just a single broker and instead broker Gloster is created.
Let's discuss what is broken.
Gloster in the next lecture by.