Architect's Tech Stack
Jun 13, 2019 · Big Data
Why Kafka Does Not Support a Master‑Slave (Write‑Read) Model and How Its Master‑Write Master‑Read Architecture Achieves Load Balancing
The article explains that although Kafka could technically implement a master‑slave (write‑read) model, it deliberately avoids it because the master‑write master‑read design already provides superior load balancing, consistency, and lower latency, making a separate read‑only replica unnecessary.
Distributed SystemsKafkaLoad Balancing
0 likes · 8 min read