Best of Change Data CaptureMarch 2026

  1. 1
    Article
    Avatar of infoqInfoQ·9w

    Netflix Automates RDS PostgreSQL to Aurora PostgreSQL Migration Across 400 Production Clusters

    Netflix built an internal automation platform to migrate nearly 400 RDS PostgreSQL production clusters to Amazon Aurora PostgreSQL with minimal downtime. The system uses a self-service workflow that handles physical read replica creation from storage snapshots, WAL replication validation, CDC slot coordination, controlled quiescence and cutover, and rollback safeguards. Because Netflix routes all database access through an Envoy-based data access layer that abstracts endpoints from application code, migrations happen transparently at the infrastructure level. A real-world case study shows how the team resolved an elevated OldestReplicationSlotLag caused by a stale logical replication slot before completing a successful migration for device certification and partner billing workloads.

  2. 2
    Article
    Avatar of debeziumDebezium·9w

    Hello Debezium Team!

    Vincenzo Santonastaso introduces himself as a new core contributor to the Debezium open source project. He shares his background as a Senior Product Engineer at lastminute.com working on distributed systems for flight booking, and prior experience at BMC Software with time-series data and forecasting. His interests center on distributed systems and event-driven architectures, and he expresses enthusiasm for contributing more deeply to Debezium.

  3. 3
    Article
    Avatar of systemdesigncodexSystem Design Codex·8w

    Inside Look at Reddit's Metadata Store

    Reddit built a unified media metadata store to consolidate scattered metadata from multiple systems into a single AWS Aurora Postgres database. The system handles 100K+ read requests per second with p50 latency of 2.6ms and p99 of 17ms. The migration used dual writes, backfill, and a Kafka-based Change Data Capture pipeline to detect and fix inconsistencies. For future scalability toward an estimated 50TB by 2030, Reddit implemented range-based partitioning using pg_partman and pg_cron, leveraging monotonically increasing post_id values to keep recent partition indexes cached in the buffer pool.