How to use Debezium with KurrentDB for CDC?

I’m exploring ways to implement Change Data Capture (CDC) in my project and I’m interested in using Debezium. However, I couldn’t find any documentation or examples about how (or if) Debezium can be integrated with CurrentDB.

  • Is there a way to connect Debezium to CurrentDB?
  • If not, what would be the recommended approach to implement CDC with CurrentDB?

Any guidance, examples, or documentation links would be greatly appreciated.

We have a short guide at our academy site:

You can take a look there first and if you have more questions we can help answer!

Thanks for the reply! I saw the guide on the academy site, but what I actually meant was using Debezium without Kafka — I’d like to stream the changes directly into EventStoreDB (ESDB).

Is there a way to connect Debezium to CurrentDB without having Kafka in the middle?

Heya. We currently don’t have sink from Debezium or a way to ingress the change events into KurrentDB. It’s something that we regularly discuss and is in our radar.

An option for you may be to manually implement a Debezium HTTP sink and append events to KurrentDB from there.

Just for my curiousity, what sort of thing are you trying to achieve? :slight_smile:

Thanks for clarifying!
In our infrastructure we don’t actually have Kafka at all — instead, we use EventStoreDB as our data bus, leveraging its persistent subscriptions/consumers.

My goal was to set up database synchronization via Debezium, but without introducing Kafka into the stack. Ideally, Debezium would stream the change events directly into ESDB, so that we can process them with persistent consumers.

1 Like