cdc

DE//AGENT currently lists 5 resources under cdc: 1 tutorial, 1 skill, 1 runbook. Everything below is derived from the live registry — counts, capabilities, verification state and security posture come from the curated records, never from marketing copy.

Also present: 1 pattern, 1 reference.

Documented learning objectives across these resources:

• Order change events deterministically — via CDC Merge Designer
• Handle deletes (tombstones) without losing history — via CDC Merge Designer
• Make the merge idempotent under replay — via CDC Merge Designer
• Read the write-ahead log instead of polling source tables — via Stream changes, not tables — CDC from Postgres into the lakehouse
• Order events by LSN and dedupe before merging — via Stream changes, not tables — CDC from Postgres into the lakehouse
• Handle tombstones without losing history — via Stream changes, not tables — CDC from Postgres into the lakehouse

These resources map to stage: Streaming (5). Follow the four-phase roadmap to place this topic inside a progression instead of learning it in isolation.

Every entry, its shape and its trust state — sorted by the registry's composite score. This table is the honest version of a marketing comparison: no sponsored placements, no unverifiable claims.

How scores are computed: source quality score.

Highest composite score first:

1. CDC Merge Designer score 39.5 — advanced
2. Postgres CDC to Lakehouse score 34.25 — advanced
3. Stream changes, not tables — CDC from Postgres into the lakehouse score 34.15 — intermediate

Scores rank provenance, completeness and trust — read how verification works before adopting anything.

Reach for these with production experience: CDC Merge Designer, Postgres CDC to Lakehouse, CDC stopped.

Security-flagged entries: CDC Merge Designer (1 flag), Postgres CDC to Lakehouse (2 flags), CDC stopped (3 flags). Flags mean the record declares capabilities like credential use or write access — read the security posture on each page before connecting.

Known limits: A nightly batch is sufficient and the source is small (Postgres CDC to Lakehouse)

• CDC Merge Designer — Produces a MERGE (or Delta/Iceberg merge) that applies inserts, updates and deletes from a CDC stream correctly, including out-of-order events and tombstones. details
• Postgres CDC to Lakehouse — Batch extraction from an OLTP database loads it and still misses deletes and mid-day changes. details
• Stream changes, not tables — CDC from Postgres into the lakehouse — The intermediate pattern that replaces nightly extraction: read the write-ahead log through Debezium, stream through Kafka, dedupe by LSN, and MERGE into Delta/Iceberg. Covers tomb… details
• Debezium Documentation — Debezium's documentation — source and sink connectors, the change-event envelope format, initial snapshots, schema history handling, and the operational pitfalls of running connect… details

Real install commands from the registry — read the source before running any of them:

npx de-agent-platform add cdc-merge-designer

CDC Merge Designer — review first

Adjacent topics: lakehouse (2 shared).

Study path: the roadmap places this topic in a progression · the scoring model explains the numbers · the trust rule catalog shows every security check these entries passed through.