Debezium
Hacker ApprovedChange data capture tool in Developer tools
Open-source change data capture tool that streams database changes to Kafka; people call it mature and stable. Common caveat: complex to configure and manage.
Open-source change data capture tool that streams database changes to Kafka; people call it mature and stable. Common caveat: complex to configure and manage.
19 people gave an opinion
- recommend it
- 14
- criticize it
- 5
- approval share
- 74%
Recommended in 5 of 13 months
- November 2025: recommended
- December 2025: recommended
- January 2026: recommended
- February 2026: recommended
- March 2026: not recommended
- April 2026: not recommended
- May 2026: not recommended
- June 2026: not recommended
- July 2026: not recommended
- August 2026: recommended
- September 2026: not recommended
- October 2026: not recommended
- November 2026: not recommended (month in progress)
Why it carries the badge
- 14 people recommend itNeeds 10 or more, met.
- 2.8 recommenders for every criticNeeds 2 to 1 or better, met.
- Recommended in 5 of 13 monthsNeeds 4 or more, met.
The same three rules apply to every product, and the badge can’t be bought. How the badge works
What people say about it
The reasons people give, with the number of comments that give each one. Open a reason to read what they said.
Why people recommend it
Each mark is one comment
Mature, stable and robust
“it is clearly the most mature, most stable option in the space, with the best prospects for long-term survival”
Comment from 17 Nov 2025 in “Listen to Database Changes Through the Postgres WAL” “Robustness is a key design goal of Debezium.”
Comment from 17 Nov 2025 in “Listen to Database Changes Through the Postgres WAL” Publishes database changes to Kafka
“This gives you a pretty seamless onramp to event streaming tools as you scale.”
Comment from 2 Nov 2025 in “"You Don't Need Kafka, Just Use Postgres" Considered Harmful” “It allows to publish all changes from the db to Kafka.”
Comment from 17 Nov 2025 in “Listen to Database Changes Through the Postgres WAL” Default choice unless strong reason
“It is probably best to use that unless there is a strong reason against.”
Comment from 17 Nov 2025 in “Listen to Database Changes Through the Postgres WAL” “Now that I know, I would recommend defaulting to it.”
Comment from 17 Nov 2025 in “Listen to Database Changes Through the Postgres WAL”
What people warn about
Each mark is one comment
Complex to set up and manage
“stitching up 3 tools - Debezium, Kafka and Spark streaming just to get the data in Iceberg was not exactly easy”
Comment from 29 Oct 2026 in “Show HN: OLake – Open-Source Postgres/MySQL/MongoDB CDC to Apache Iceberg” “the setup alone in a kubernetes cluster with strimzi kafka connect”
Comment from 18 Jul 2026 in “Show HN: Ingestr CDC – open-source CDC replication in Go” “can be complex to configure and manage”
Comment from 31 May 2026 in “Made a Tool to Streams Changes from Microsoft SQL Server to Apache Kafka” Needs Kafka and other infrastructure
“stitching up 3 tools - Debezium, Kafka and Spark streaming just to get the data in Iceberg was not exactly easy”
Comment from 29 Oct 2026 in “Show HN: OLake – Open-Source Postgres/MySQL/MongoDB CDC to Apache Iceberg” “the setup alone in a kubernetes cluster with strimzi kafka connect”
Comment from 18 Jul 2026 in “Show HN: Ingestr CDC – open-source CDC replication in Go”
What people said
18 of the 22 comments that mention it, newest first. Each links to the original comment.
“stitching up 3 tools - Debezium, Kafka and Spark streaming just to get the data in Iceberg was not exactly easy”
“Kafka/Debezium/Flink for streaming data”
“they are all fragile to schema updates in some direction”
“the setup alone in a kubernetes cluster with strimzi kafka connect”
“can be complex to configure and manage”
“Debezium + CDC makes this quite clean.”
“It works but it will be better to not have to do that”
“we're really happy with Debezium in general”
“I helped a company that is build averse move off of Fivetran to Debezium”
“Now that I know, I would recommend defaulting to it.”
“It is probably best to use that unless there is a strong reason against.”
“it is clearly the most mature, most stable option in the space, with the best prospects for long-term survival”
“Debezium generally produces each change event exactly once if there are no unclean connector shut-downs.”
“Robustness is a key design goal of Debezium.”
“my experience is the Debezium project doesn’t really guarantee exactly-once delivery.”
“It allows to publish all changes from the db to Kafka.”
“There's pros and cons to either way of running Debezium.”
“This gives you a pretty seamless onramp to event streaming tools as you scale.”
Counts come from 1,795,640 Hacker News comments, November 2025 to November 2026. How we count. Report a mistake.