# Debezium Change Data Capture for Pipelines
Status: public
Confidence: medium (0.725) (verified)
Last verified: 2026-06-02
Generation: ai_structured


## TL;DR

Debezium CDC turns database changes into event streams that data agents can use for freshness, lineage, and incremental processing.

## Core Explanation

Batch pipelines often lag behind source systems. Change data capture listens to database changes and emits events as rows are inserted, updated, or deleted. This gives downstream systems a way to update indexes, caches, feature stores, and data products without full reloads.

For agents, CDC evidence matters because it explains why a dataset changed and whether a retrieval or analytics index is current. The agent should inspect connector status, offsets, schema changes, and snapshot state before trusting pipeline freshness.

## Source-Mapped Facts

- Debezium documentation describes Debezium as a distributed platform that converts information from existing databases into event streams. ([source](https://debezium.io/documentation/reference/stable/tutorial.html))
- Debezium MySQL connector documentation describes capturing row-level changes in a MySQL database. ([source](https://debezium.io/documentation/reference/stable/connectors/mysql.html))
- Debezium signaling documentation describes sending signals to Debezium connectors. ([source](https://debezium.io/documentation/reference/stable/configuration/signalling.html))

## Further Reading

- [Debezium Tutorial](https://debezium.io/documentation/reference/stable/tutorial.html)
- [Debezium MySQL Connector](https://debezium.io/documentation/reference/stable/connectors/mysql.html)
- [Debezium Signaling](https://debezium.io/documentation/reference/stable/configuration/signalling.html)