WEBVTT 00:04.180 --> 00:09.380 Listen, I'll shortly summarize what we did here in this example, we have started the basic algebra 00:09.400 --> 00:11.950 and basic brolga afterwords. 00:11.950 --> 00:18.740 We agreed that the new topic called Animals with three partitions and obligation factor one next week 00:18.740 --> 00:24.490 will produce some messages to this topic and observed log's here using studier code. 00:24.490 --> 00:29.620 And we have seen that the old messages, we are equally spread across all professions. 00:29.800 --> 00:35.110 There are basically three different folders for partitions of this particular topic, and by exploring 00:35.170 --> 00:39.990 log files, you are able to see where each particular message has arrived. 00:40.300 --> 00:45.760 We have made important conclusion and that is a asynchronous process of consumption of messages. 00:46.270 --> 00:52.900 If there are multiple partitions in particular topic, then consumers might receive messages not in 00:52.900 --> 00:53.890 the same order. 00:54.040 --> 00:56.950 They were sent by specific producer. 00:57.370 --> 01:03.820 But on the other hand, if you read messages from a particular partition, then of course you will consume 01:03.820 --> 01:10.660 messages one by one, starting from a lower offset and deal last offset because order of the messages 01:10.660 --> 01:13.540 inside of a particular partition doesn't change. 01:13.930 --> 01:19.960 Also, we have used this topic segment and read the details about Dobek and we have read the dailies 01:19.960 --> 01:23.050 about consumer offsets topic and animals topic. 01:23.380 --> 01:30.280 And you have seen that this animals topic has actually three partitions here with this output and leader 01:30.280 --> 01:35.800 is the same for every partition level because for now we have only single brolga. 01:36.430 --> 01:37.720 This all for this example. 01:37.720 --> 01:38.770 I hope you liked it. 01:38.770 --> 01:44.800 And in the next example, we will start multiple programs, namely three brockers, but we will still 01:44.800 --> 01:46.690 use just single Kebra. 01:46.960 --> 01:52.810 And afterwards in that setup, we will create the new topic and explore how messages will be spread 01:52.810 --> 01:54.250 among different brockers. 01:54.250 --> 01:56.380 So see you in the next example by byte.