It's Okay To Store Data In Kafka
Sep 15, 2017Jay Kreps

Summary
This post argues that Kafka is designed for long-term data storage, not just messaging. It highlights use cases like event sourcing, materialized views for stream processing, and Change Data Capture (CDC) where Kafka's log compaction and persistent storage are beneficial. The author contrasts Kafka's architecture (distributed filesystem/database-like) with traditional message queues, emphasizing its ability to store, replicate, and serve data reliably. It also touches on the operational rigor required when treating Kafka as a primary store and mentions Confluent's support and hosted services.
More from the Kafka Infinite Storage trail
- Apache Kafka® vs Confluent Cloud: Latency Benchmarking Results
- Lowering Kafka Costs by Improving Utilization and Ease of Use
- Kafka Storage That’s 10x More Scalable and Elastic with Confluent
- Making Confluent Cloud 10x More Elastic Than Apache Kafka | Confluent Making Confluent Cloud 10x More Elastic Than Apache Kafka
- How Instacart Used Confluent to Scale 10 Years of Growth in 6 Weeks