Loading content
Change Data Capture (CDC) enables the monitoring of changes in data and the immediate execution of updates. This is particularly useful for data integration scenarios where data needs to be synchronized in real time.
Use this profile to understand the building block briefly, place it in the model, and switch to the 360° assessment when needed.
Theoretical construct: explains a term, principle, or mental model.
What organizes, connects, or makes decisions possible.
Change Data Capture records changes to data records and exposes them as events or a change stream for downstream systems.
CDC grew from database replication, change logs, and the need to distribute data promptly. Databases such as Oracle and SQL Server provide their own tracking or log-based mechanisms; Debezium made log-based CDC broadly accessible as an open-source platform.
The database writes changes to a trail. CDC reads that trail, turns inserts, updates, and deletes into events, and delivers them to consumers. Ordering, replay, and schema evolution still need explicit handling.
The source from which CDC reads database changes.
A message about inserting, updating, or deleting a record.
A downstream system that processes change events.
CDC keeps indexes, warehouses, and services synchronized without repeatedly copying whole tables. It does not by itself guarantee business consistency or successful consumer processing.
Where this building block is located in the topic model.
Explore how this building block connects to concepts, methods, technologies, and tools.
These sources establish the term and its professional meaning.
All direct connections of the current building block in a compact text view.
This classification shows where the building block typically matters, how demanding it is, and what kind of impact it has in the model.
The level within the organization (enterprise, domain, team) at which the AssetBlock is applied.