Skip to main content
PreparationZone Logo
PrepZone

Local Kafka Cluster with Docker Compose

KRaft-mode three-broker compose stack for VaultCommerce local development with Schema Registry.

Pass checkpoint below

Why this matters

  • Every engineer runs docker compose up kafka — identical topic creation scripts as staging.
  • KRaft 3-broker compose matches production metadata behavior at laptop scale.
  • Schema Registry + AKHQ for debugging Avro payloads.
  • Faster iteration than shared dev cluster contention.
ProducersOrder, payment services
Broker cluster3+ brokers, KRaft
Consumer groupsInventory, analytics
Topic: vaultcommerce.orders.placed.v1
Partition 0Leader on broker-1
Partition 1Leader on broker-2
Partition 2Leader on broker-3
Producers write to topic partitions on brokers. Consumers read via consumer groups.

Compose topology

3 Kafka brokers in KRaft combined mode, 1 Schema Registry, 1 AKHQ. Host ports 9092/9093/9094 for bootstrap. VaultCommerce docker/compose/kafka.yml seeds topics via kafka-init one-shot container.

Key points

  • KRaft combined mode — broker + controller in one container for dev
  • Schema Registry — local Avro schema registration on push
  • kafka-init — container that creates topics after brokers healthy
  • AKHQ / Kafka UI — browse topics, consumer groups, messages
  • advertised.listeners — PLAINTEXT://localhost:9092 for host access

The rest of this guide is part of Pro

Free covers every fresher guide in full. Pro unlocks Senior, Staff and Architect guides across every track.

Still to come · 2 sections

  • Application wiring
  • VaultCommerce rollout checklist

Test yourself

Answer these before moving on — recall is what makes it stick.