Yandex Cloud
Search
Discuss with expertTry it for free
  • Customer Stories
  • Documentation
  • Blog
  • All Services
    • Cloud Interconnect
    • Cloud Backup
    • Cloud Registry
    • Yandex AI Studio
    • Compute Cloud
    • Object Storage
    • Managed Service for Kubernetes®
    • Yandex BareMetal
    • Smart Web Security
    • Security Deck
    • Managed Service for PostgreSQL
    • Managed Service for ClickHouse®
    • Monium
    • Cloud CDN
    • Network Load Balancer
    • Virtual Private Cloud
    • Cloud DNS
    • Application Load Balancer
    • Yandex Cloud Video
    • Stackland
    • Yandex Cloud Router
    • Yandex Managed Service for Trino
    • Managed Service for MySQL®
    • Managed Service for Valkey™
    • Managed Service for Apache Spark™
    • Yandex StoreDoc
    • Managed Service for OpenSearch
    • Managed Service for Apache Kafka®
    • Data Transfer
    • Yandex MPP Analytics Engine for PostgreSQL
    • Yandex Managed Service for Apache Airflow®
    • Data Processing
    • Yandex MetaData Hub
    • Managed Service for YDB
    • Managed Service for Sharded PostgreSQL
    • Managed Service for YTsaurus
    • Yandex WebSQL
    • DataLens
    • Yandex Search API
    • SpeechSense
    • SpeechKit
    • DataSphere
    • Vision OCR
    • Translate
    • Yandex Identity Hub
    • Key Management Service
    • Certificate Manager
    • Yandex Lockbox
    • Audit Trails
    • SmartCaptcha
    • Cloud Desktop
    • SourceCraft Code Assistant
    • Container Registry
    • Managed Service for GitLab
    • Managed Service for Prometheus®
    • Cloud Functions
    • API Gateway
    • Yandex Cloud Postbox
    • Message Queue
    • Serverless Integrations
    • IoT Core
    • Data Streams
    • Serverless Containers
    • Cloud Notification Service
    • Yandex Query
    • Identity and Access Management
    • Yandex Cloud Console
    • Resource Manager
    • Yandex Cloud Billing
    • Yandex Cloud Quota Manager
    • Cloud Apps
  • System Status
  • Marketplace
    • Featured
    • Infrastructure & Network
    • Data Platform
    • AI for business
    • Security
    • DevOps tools
    • Serverless
    • Monitoring & Resources
  • All Solutions
    • By industry
    • By use case
    • Economics and Pricing
    • Security
    • Technical Support
    • Start testing with double trial credits
    • Cloud credits to scale your IT product
    • Gateway to Russia
    • Cloud for Startups
    • Center for Technologies and Society
    • Yandex Cloud Partner program
    • Price calculator
    • Pricing plans
  • Customer Stories
  • Documentation
  • Blog
© 2026 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
    • User roles
    • Managing data schemas
    • Web interface for Apache Kafka®
    • APIs in Managed Service for Apache Kafka®
    • Host classes
    • High availability clusters
    • Networking in Managed Service for Apache Kafka®
    • Quotas and limits
    • Storage in Managed Service for Apache Kafka®
    • Connectors
    • Maintenance
    • Apache Kafka® settings
    • Apache Kafka® versioning policy
  • 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 July 16, 2026
View in Markdown

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 on how brokers handle messages, see the this Apache Kafka® guide.

Was the article helpful?

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