
7/19/2017 · Ben Stopford
What this post added
This post introduces Apache Kafka as a message backbone for service architectures, contrasting it with traditional message brokers. It details Kafka's log-structured design, linear scalability, load segregation via quotas, strong ordering guarantees (using keys and single-partition topics), durability through replication (with configuration recommendations like `min.insync.replicas`), and load balancing of services through partition assignment. It also discusses producer configuration for retries (`max.inflight.requests.per.connection`) and broker configurations for durability (`log.flush.interval.messages`).