Yandex Cloud
Search
Contact UsGet started
  • Blog
  • Pricing
  • Documentation
  • All Services
  • System Status
    • Featured
    • Infrastructure & Network
    • Data Platform
    • Containers
    • Developer tools
    • Serverless
    • Security
    • Monitoring & Resources
    • ML & AI
    • Business tools
  • All Solutions
    • By industry
    • By use case
    • Economics and Pricing
    • Security
    • Technical Support
    • Customer Stories
    • Cloud credits to scale your IT product
    • Gateway to Russia
    • Cloud for Startups
    • Education and Science
    • Yandex Cloud Partner program
  • Blog
  • Pricing
  • Documentation
© 2025 Direct Cursus Technology L.L.C.
Yandex Managed Service for Apache Kafka®
  • Getting started
    • Resource relationships
    • Topics and partitions
    • Brokers
    • KRaft protocol
    • Producers and consumers
    • Managing data schemas
    • APIs in Managed Service for Apache Kafka®
    • Host classes
    • Networking in Managed Service for Apache Kafka®
    • Quotas and limits
    • Storage in Managed Service for Apache Kafka®
    • Connectors
    • Maintenance
    • Apache Kafka® settings
  • Access management
  • Pricing policy
  • Terraform reference
  • Yandex Monitoring metrics
  • Audit Trails events
  • Public materials
  • Release notes
  • FAQ
  1. Concepts
  2. Brokers

Brokers

Written by
Yandex Cloud
Updated at September 14, 2023

Brokers are hosts in a Managed Service for Apache Kafka® cluster where Apache Kafka® topics and partitions reside.

Topic partitions store messages that clients (producers and consumers) work with.

A broker performs the following functions:

  • Accepts connections from clients.

  • Provides clients with information about topics, partitions, and other brokers in the cluster.

  • Receives requests to read and write messages from clients.

  • Stores messages.

  • Participates in partition replication.

    Each replicated partition has a leader broker that accepts read and write requests, and multiple follower brokers that replicate the leader data. The number of followers depends on the replication factor, i.e., the number that determines how many replicas of partition data a cluster has. For example, if the replication factor equals to 1, a partition will have no followers; if it is 2, it will have one follower, if 3, two followers, etc.

For more information about how brokers handle messages, see the Apache Kafka® documentation.

Was the article helpful?

Previous
Topics and partitions
Next
KRaft protocol
© 2025 Direct Cursus Technology L.L.C.