cdc-debezium

Set up Debezium CDC pipelines exporting database row changes to Kafka.

14|1|Updated May 5, 2026
One-click install
npx skills add https://github.com/ivanshamaev/de-agent-skills --skill cdc-debezium
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: cdc-debezium
Source: https://github.com/ivanshamaev/de-agent-skills/tree/main/skills/cdc_debezium
Command: npx skills add https://github.com/ivanshamaev/de-agent-skills --skill cdc-debezium

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you set up and operate reliable Change Data Capture (CDC) pipelines with Debezium so database changes can be streamed to Kafka and downstream sinks without missing updates or duplicating data.

Core Features & Use Cases

  • Debezium connector setup: Configure PostgreSQL/MySQL/Oracle CDC connectors, including replication slots, publications, binlog settings, and schema history for DDL propagation.
  • CDC event interpretation: Understand Debezium change event envelopes (before/after/op/source), snapshot modes, tombstone behavior, and truncation events.
  • Production-grade delivery patterns: Implement the outbox pattern, apply Single Message Transforms (SMTs) like ExtractNewRecordState and routing, and integrate with Flink/Spark/dbt and Iceberg/Delta sinks using upsert and CDC semantics.

Quick Start

Ask the AI to generate a complete PostgreSQL Debezium connector configuration for tables customers and orders using snapshot.mode initial, ExtractNewRecordState flattening, DLQ enabled, and Iceberg upsert semantics for a lakehouse sink.

Frequently Asked Questions about cdc-debezium

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I set up a Debezium CDC pipeline to stream PostgreSQL changes to Kafka?

To set up Debezium CDC for PostgreSQL, configure the connector with appropriate replication slots, publications, and schema history for DDL propagation. You need Kafka Connect deployed, then use snapshot.mode initial to capture existing data before streaming ongoing row changes.

What is the outbox pattern in Debezium and when should I use it for CDC?

The outbox pattern in Debezium ensures transactional CDC by writing change events to a dedicated outbox table within the same database transaction. Use it to guarantee exactly-once delivery semantics and prevent data inconsistency between source tables and Kafka topics.

How do I handle delete tombstones and schema evolution in Kafka Connect CDC pipelines?

Handle delete tombstones by configuring sink connectors to process null-value Kafka messages as deletions, and manage schema evolution using schema history topics for DDL propagation. Apply Single Message Transforms like ExtractNewRecordState to shape Debezium change events correctly.

Can I use Debezium CDC events with Flink streaming and Iceberg lakehouse sinks?

Yes, Debezium CDC events can integrate with Flink streaming and Iceberg lakehouse sinks using upsert and CDC semantics. This requires applying ExtractNewRecordState flattening transforms and configuring idempotent sink connectors to handle change event parsing correctly.

Does Debezium CDC work with MySQL and Oracle replication scenarios?

Debezium CDC supports MySQL and Oracle replication by configuring binlog settings and schema history for DDL propagation. Each database requires specific connector prerequisites and snapshot modes to ensure correct change event capture and structured export to Kafka topics.