Glossary · System coordination, integration and orchestration
Change data capture (CDC)
Also known as: CDC, change-data capture
German: Änderungsdatenerfassung (CDC)
In data integration, change data capture (CDC) is a technique that detects inserts, updates and deletes in a source database, typically by reading its transaction log, and delivers them as a stream of change events to other systems.
- System integration
In one sentence
Change data capture detects inserts, updates and deletes in a source database and streams them as change events to other systems.
Example
Every change to the material master in the ERP database is captured by CDC and published to the event broker, so the MES updates its copy within seconds.
How it applies
- Integration: CDC avoids repeated bulk exports and puts little extra load on the source application. Consumers receive changes in commit order, which supports Data replication and event-driven integration.
- Engineering: Plan for schema changes in the source, for consumers that fall behind and for the initial load before change streaming starts. Consumers of CDC data are usually eventually consistent (see Eventual consistency) with the source.
- Documentation: Document which tables are captured, which system is the Source of truth for each data item and how long change history is retained. Personal data in captured tables may need separate protection.
CDC vs. data replication
CDC is a way of detecting and delivering changes. Data replication is the broader goal of keeping copies of data in sync; it can use CDC, snapshots or application-level messages.