Debezium
Change data capture for a variety of databases. Please log issues at https://github.com/debezium/dbz/issues. observed · 2026-08-28
Health v2 · maintenance only
77/100
- Activity 99
- Release rhythm 35
- Longevity 100
Flags: no_releases
How is this computed?
round(0.45*activity + 0.35*rhythm + 0.20*longevity); archived -> min(score, 10) — computed 2026-09-03. Adoption (stars, forks) is never an input.
- gap_med: n/a
- age_days: 3876
- days_rel: n/a
- days_push: 7
- n_releases_24m: 0
Adoption not part of the score
13049 stars · 3017 forks observed · 2026-08-28
What it is AI-extracted, prompt v1, taxonomy v1, 2026-08-29, confidence not recorded
Debezium is an open source distributed platform for change data capture (CDC) that streams row-level database changes as events, most commonly via Apache Kafka Connect source connectors. It uses log-based CDC to capture inserts, updates, and deletes with low latency, durable offset tracking, and a unified change event model across many databases.
Use cases
- stream database changes to kafka in real time
- keep elasticsearch search index in sync with a database
- invalidate caches when rows change
- implement the transactional outbox pattern for microservices
- replicate data from mysql or postgres to a data warehouse
- capture deletes and old row state without triggers or last-updated columns
- build event-driven services that react to data changes
When to choose
- you need reliable, ordered, low-latency change data capture from a supported database
- you already run or can deploy Apache Kafka / Kafka Connect
- you want to avoid polling, dual writes, or database triggers
- you need durable event history so consumers can go down and resume without missing events
When to avoid
- you have no Kafka or event-streaming infrastructure and only need simple one-off ETL jobs
- your database is not among the supported connectors
- you only need batch data sync on a schedule rather than streaming changes
- you cannot grant the replication/log-reading privileges Debezium requires on the source database
Facets
library · maturity stable
streaming etl database message-queue middleware databases big-data microservices developer-tools jvm self-hosted cloud change-data-capture cdc kafka-connect apache-kafka event-streaming data-pipeline log-based-cdc mysql postgresql oracle sql-server mongodb outbox-pattern data-engineering docker kubernetes
10 sources
- readme: https://github.com/debezium/debezium · fetched 2026-08-28 · 35eb09473da8
- homepage: https://debezium.io · fetched 2026-08-29 · 2ea7b075ea21
- site_page: https://debezium.io/documentation/faq · fetched 2026-08-29 · 96f25a7714ae
- site_page: https://debezium.io/documentation · fetched 2026-08-29 · f3d68fd92226
- site_page: https://debezium.io/documentation/reference/3.6/tutorial.html · fetched 2026-08-29 · 01c5b6db4e2b
- site_page: https://debezium.io/documentation/reference/stable/features.html · fetched 2026-08-29 · cfccb1164541
- site_page: https://debezium.io/documentation/reference/stable/architecture.html · fetched 2026-08-29 · 9510903474fd
- site_page: https://debezium.io/releases · fetched 2026-08-29 · 2d352fd0e238
- site_page: https://debezium.io/releases/3.6 · fetched 2026-08-29 · 5786eba3114e
- site_page: https://debezium.io/releases/3.7 · fetched 2026-08-29 · eb3d214e97be
Member repositories
| Repository | Role | Health v2 |
|---|---|---|
| debezium/debezium | main | 77 |
| debezium/debezium-examples | examples | 77 |
For agents
markdown · JSON · MCP: product_card(name="debezium/debezium")
Data as of 2026-08-30T08:39:29.467469+00:00 · Report a problem