Writing
How change data capture fails in practice, from the public record.
Polling an events table can skip an event. Nothing will tell you.
Projections that poll an events table by ID can skip a committed event and still report they are caught up. Why it happens, what the common fixes cost, and how to check your own.
Your CDC pipeline stopped. Why is your database still filling up?
Stopping a CDC connector does not necessarily release the history it needs. Follow a PostgreSQL replication slot from a paused pipeline to a storage decision.
Your CDC pipeline saved its place. Why is the history gone?
When a CDC pipeline restarts, can it catch up from its saved position, or must it rebuild the destination? The answer changes the work recovery requires.
Your CDC pipeline says RUNNING. Your data stopped moving.
Seven ways CDC delivery can fail without a useful status signal, and the progress metrics to monitor alongside task state.
I analyzed 1,965 CDC bug reports. Here is what actually breaks, ranked.
What 1,965 public CDC bug reports say breaks most often, ranked by mechanism: lost positions, silent stalls, schema changes, and the failures a bug tracker cannot count.