Learn
Debezium
2 registry resources · 1 skill, 1 project · roadmap: Streaming
What this topic covers
DE//AGENT currently lists 2 resources under Debezium: 1 skill, 1 project. Everything below is derived from the live registry — counts, capabilities, verification state and security posture come from the curated records, never from marketing copy.
What you can learn here
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
- Configure a logical replication slot safely — via Postgres → CDC → Kafka → Lakehouse
- Order events by LSN and dedupe before merging — via Postgres → CDC → Kafka → Lakehouse
- Handle tombstones without losing history — via Postgres → CDC → Kafka → Lakehouse
Where this fits in the learning roadmap
These resources map to stage: Streaming (2). Follow the four-phase roadmap to place this topic inside a progression instead of learning it in isolation.
Compare the registry's options
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.
| Resource | Type | Difficulty | Verification | Score |
|---|---|---|---|---|
| CDC Merge Designer | Skill | advanced | community flags | 39.5 |
| Postgres → CDC → Kafka → Lakehouse | Project | advanced | community flags | 33.65 |
How scores are computed: source quality score.
Where to start
Highest composite score first:
- CDC Merge Designer score 39.5 — advanced
- Postgres → CDC → Kafka → Lakehouse score 33.65 — advanced
Scores rank provenance, completeness and trust — read how verification works before adopting anything.
Good fits
Reach for these with production experience: CDC Merge Designer, Postgres → CDC → Kafka → Lakehouse.
Cautions and limitations
Security-flagged entries: CDC Merge Designer (1 flag), Postgres → CDC → Kafka → Lakehouse (4 flags). Flags mean the record declares capabilities like credential use or write access — read the security posture on each page before connecting.
Production use cases
- 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 → Kafka → Lakehouse — Capture changes from Postgres with Debezium, stream through Kafka, and merge into a lakehouse table with correct ordering, deletes and replay safety. details
Install and inspect
Real install commands from the registry — read the source before running any of them:
npx de-agent-platform add cdc-merge-designerCDC Merge Designer — review first
Further study
Official source: Debezium (license: Apache-2.0) — start there for the canonical documentation, then come back for the vetted registry entries.
Adjacent topics: Delta Lake (2 shared), Apache Iceberg (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.
Full resource list
| Resource | Type | Score |
|---|---|---|
| CDC Merge Designer | Skill | 39.5 |
| Postgres → CDC → Kafka → Lakehouse | Project | 33.65 |