WEBVTT 00:04.280 --> 00:10.370 Now, there are two consumers up and running here, and we have just verified that both of them received 00:10.370 --> 00:14.230 new massages, but we have just single producer here. 00:14.570 --> 00:20.300 Let's not try to run one more producer by keeping this comment and run it in a new time. 00:20.300 --> 00:20.860 No window. 00:21.170 --> 00:24.740 Let's make this window smaller like so it will be a producer. 00:24.750 --> 00:25.130 No. 00:25.130 --> 00:32.540 One, open the window, make it the smaller and place it somewhere here like salt. 00:32.660 --> 00:34.420 And let's see the folder. 00:35.720 --> 00:41.390 Clear terminal and start new producer with same command as we have used for starting of this producer 00:41.660 --> 00:46.860 will enter here and now we are able to produce some messages from this producer. 00:47.210 --> 00:54.380 Let's write another name, for example, Barcelona press enter message was sent and it was successfully 00:54.380 --> 00:57.020 received by both consumers. 00:57.410 --> 01:00.040 And here was another important outcome. 01:00.230 --> 01:04.370 Neither consumers nor producers know about each other. 01:04.730 --> 01:12.110 It means that this producer doesn't know anything about existence of those consumers and about other 01:12.110 --> 01:13.250 producers as well. 01:13.650 --> 01:17.230 He does just perform its own job, nothing else. 01:17.720 --> 01:19.910 Same I can say about this producer. 01:20.030 --> 01:24.680 It produces messages without knowing about all the producers or consumers. 01:25.190 --> 01:30.500 And consumers don't care about producers that produced those particular messages. 01:30.860 --> 01:36.380 They just consume messages from one centralized storage from coffeecake last time. 01:36.650 --> 01:38.960 And that is the beauty of Kafka architecture. 01:39.170 --> 01:45.980 Producers and consumers might appear and may go, but as long as messages are stored in centralized 01:45.980 --> 01:49.430 storage in coffeecake year, they may be consumed by consumers. 01:49.550 --> 01:53.640 And new producers may send new messages to this Kafka cluster. 01:53.870 --> 01:56.920 For example, let's try to stop this Kafka producer. 01:57.170 --> 01:57.950 It will stopped. 01:57.950 --> 02:03.410 But this action didn't affect in any way those consumers or this producer. 02:03.590 --> 02:05.480 They are still up and running. 02:05.660 --> 02:10.850 And I'm able to produce another message, for example, here by typing, let's say, Madrid. 02:11.600 --> 02:14.600 And this message will be received again by both consumers. 02:14.930 --> 02:20.120 I can start this producer once again and send another city name, for example, Toronto. 02:20.930 --> 02:23.660 It will be consumed as before by both consumers. 02:23.900 --> 02:28.040 And to those consumers don't care about presents or producers. 02:28.490 --> 02:30.440 They do just simple job. 02:30.590 --> 02:34.910 Get new messages from Kafka, Glouster, Death it OK? 02:35.090 --> 02:41.690 At this moment you should have really nice understanding of what Kafka is and what it actually does. 02:42.020 --> 02:47.780 Also, you understand what a producer and what a consumer producers sent messages to Kafka. 02:47.780 --> 02:51.110 Gloster and consumers consume those messages. 02:51.590 --> 02:59.570 Nola's Prasit and Next lets us or some other questions like where Kafka basically stores all those messages, 02:59.660 --> 03:04.640 because as we have seen before, you are able to read the messages from the very beginning. 03:04.790 --> 03:10.370 And that means that somewhere Kafka stores all messages that were sent to a particular topic. 03:10.700 --> 03:12.080 Let's explore it next. 03:12.080 --> 03:12.610 Bye bye.