Blog
Deep dives on transaction log processing, Change Data Capture, and the infrastructure that moves data in real time.
What a Lost ACK Means for Data Delivery
A lost acknowledgment leaves destination state unknown. Learn how retries, Kafka producer settings, and recovery policy shape a safe delivery decision.
When Can a Data Pipeline Safely Delete History?
Learn when source WAL, replay archives, audit records, and recovery logs can be deleted without breaking delivery or recovery.
What PostgreSQL wal_level Changes, and What It Does Not
Learn what PostgreSQL wal_level enables, why a restart is required, and how slot state separates source settings from stream operation.
Logical vs Physical Replication: When to Use Each
PostgreSQL offers two replication modes with different trade-offs. Learn when to use physical replication, when to use logical, and when to run both.
PostgreSQL WAL: How It Works
Learn how PostgreSQL's Write-Ahead Log works, from WAL records and full-page writes to checkpoints, replication slots, and monitoring queries.
What is Change Data Capture (CDC)?
Change Data Capture streams database changes to downstream systems in real time. Learn how CDC works, the three approaches, and when to use each.
What is a Transaction Log? WAL, Binlog, and Oplog Explained
Transaction logs power crash recovery, replication, and CDC. Learn how PostgreSQL WAL, MySQL binlog, and MongoDB oplog work and how they differ.
One processor. Six transaction log functions.
Move committed data through one controlled path, with explicit ordering, delivery, and recovery boundaries.