Apache Kafka® Broker Failures & Other Outages
Apr 27, 2021Jakub Korab

Summary
This post details the impact of Kafka broker and cluster failures on applications, emphasizing the need for robust operational practices and application-level resilience. It outlines best practices for preventing outages (redundancy, distribution, replication, monitoring, upgrades, automation) and discusses how different application architectures (entry points vs. polling, synchronous vs. asynchronous sends) are affected by extended outages. It also describes the characteristics of extended outages and how client configurations influence error handling, providing a framework for designing applications that can gracefully handle service interruptions.
More from the Confluent Cloud Availability and Resilience trail
- Cost of Apache Kafka® Migrations: Estimate & Reduce Streaming Platform Costs
- Building for 99.99% Uptime on Confluent Cloud
- Testing & Maintaining Apache Kafka® DR and HA Readiness
- Cut the Costs of Hosted Kafka with Confluent Cloud’s Price Guarantee
- Hosted Apache Kafka® vs. Fully Managed With Confluent Cloud