A broker is a proxy server and a service provider.
In CKafka, a broker is an individual CKafka server mainly used to receive messages sent by producers, assign offsets, and save messages to disks. It also receives requests from consumers and other brokers, processes them based on request types, and returns responses.
For more information, please see Cloud Kafka.
A partition is a physical concept for storing messages. It is the basis for CKafka's horizontal scalability. The parallel processing power of CKafka can be increased by adding servers and assigning partitions on them.
An offset is a unique identifier of a message in a partition.
A replica is a message backup. Each partition can have multiple replicas that have the same messages (this is subject to the sync mechanism as replicas may not be exactly the same at the same time).
Each partition in CKafka has at least two replicas to ensure high service availability.
A consumer group is a set of consumers. In CKafka, multiple consumers can form a consumer group, and each consumer can only belong to one consumer group. Consumer group guarantees that each partition under the topic to which it subscribes to is assigned to exactly one consumer in the group.
You are recommended to specify a consumer group ID when messages are consumed. Otherwise, CKafka system will randomly generate a consumer group, which may reach the maximum number of consumer groups allowed. For more information, please see CKafka Billing Overview.
Cloud Kafka (CKafka) is a distributed, high-throughput, and highly scalable messaging system fully compatible with open-source Kafka API (v0.9 and 0.10). Based on the publish/subscribe model, it enables async interaction between producer and consumer by decoupling the messages and thereby eliminates the wait time on both sides. It supports data compression and offline/real-time data processing, making it ideal for scenarios such as collection of compressed logs and aggregation of monitoring data.
ZooKeeper is a software program that provides centralized services for distributed applications, such as configuration maintenance, domain name service, distributed sync, and group service. In CKafka, it is mainly used to store the metadata of the cluster, elect leaders, and tolerate faults.