So far, you have gained a basic understanding of the Kafka architecture. There is a producer which writes data to a topic and there is a consumer which reads data from these topics. In the next video, let’s gain a detailed understanding of topics.
In the last video, you learnt that topics are organised collections of data. Each topic should have a unique name, and these can be multiple topics depending on the storage capacity. These topics are further divided into partitions, which are then stored in brokers. Partitions of a topic are stored across different brokers. A single topic can be subscribed by more than one consumer.
In the upcoming video, let’s learn about partitions in more detail.
In the previous video, you understood the concept of partitions and learnt how they are stored across different brokers. When a message is being pushed into any partition, it is assigned an offset, which is an incremental ID. The message that is pushed first will have a lower offset, and the one that is pushed later will have a higher offset, and the one that is pushed later will have a higher offset value. When messages are being read from partitions, they can only be read in the order in which they were pushed. Also, the message which are stored in topics partitions are immutable.
You will learn about how to create Kafka topics and partitions in the next session.
Additional Reading
Topics and Partitions – To know more about topics and partitions, you can refer to this link.
Report an error
Topics and Partitions –