change data capture (CDC)
Publish source-data changes so downstream systems can follow them.
Use this when A search index or warehouse must follow database updates without repeated full scans.
without the term
“Keep the search index following inserts, updates, and deletes from the database, including after a restart.”
with the term · How do you ask a model for change data capture (CDC)?
Use CDC for this projection. Verify snapshot handoff, restart recovery, duplicate handling, and delete propagation.
What is change data capture (CDC)?
CDC captures inserts, updates, and deletes and exposes change events, often from a database log. Snapshot initialization, offsets, ordering scope, and delivery semantics depend on the connector.
Why does change data capture (CDC) matter when vibe coding?
An agent can process each event as unique and double-apply a change after a restart.
How do you do change data capture (CDC)?
Define the snapshot-to-stream handoff and durable offsets. Test restart, duplicate delivery, deletes, schema changes, and reconciliation with the source.
What goes wrong with change data capture (CDC)?
CDC is not an automatic end-to-end exactly-once guarantee or an application business-event contract.
Sources for this entry
- Debezium: Architecture
Connectors capture database changes and publish change events; consumers must account for delivery and recovery behavior.
Sources checked . Source checks do not establish human editorial approval. How we check content.