Publishing with Apache Kafka at The New York Times | Confluent

What this post added

This post details The New York Times' implementation of a log-based architecture using Apache Kafka as the 'Monolog' to store all published content. It contrasts this with previous API-based approaches, highlighting the benefits of a log as the source of truth for creating materialized views, simplifying schema evolution, and enabling immutable deployments of stateful systems. The post also explains why Kafka's log retention and ordered consumption capabilities are crucial for this use case, differentiating it from message brokers like Google Pub/Sub and AWS SNS/SQS/Kinesis.