Debezium Blog
When I started working on Debezium, two questions came to mind: Is it possible to build a native version of Debezium? Can I receive change data capture (CDC) events directly inside my microservice without relying on additional infrastructure?
This led us to work on a new Debezium stream: I’m excited to announce the first release of Debezium Extensions for Quarkus!
Debezium 3.3.0.Alpha1 introduces an exciting wave of innovation, including exactly-once semantics for core connectors and a brand new CockroachDB connector led by the community. Featuring support for emerging data types, deeper Quarkus integration, and enhanced tooling, this release raises the bar for modern change data capture solutions. Ready to see what’s new? Let’s dive in.
Remember when debugging streaming data pipelines felt like playing detective in a crime scene where the evidence kept moving? Well, grab your magnifying glass because we’re about to turn you into Sherlock Holmes of the streaming world. After our introduction to OpenLineage integration with Debezium, it’s time to roll up our sleeves and get our hands dirty with some real detective work. We’ll build a complete order processing pipeline that captures database changes with Debezium, processes them through Apache Flink, and tracks every breadcrumb of data lineage using OpenLineage and Marquez – because losing track of your data is like losing your keys, except infinitely more embarrassing in production.
Case definition
In this showcase, we demonstrate how to leverage lineage metadata to troubleshoot issues in data pipelines. Our e-commerce order processing pipeline, despite its simplicity, effectively illustrates the benefits of lineage metadata for operational monitoring and debugging. We will simulate a configuration change in the Debezium connectors that causes the order processing job to skip records. Using the lineage graph, we’ll navigate through the pipeline components to identify the root cause of the problem and understand how metadata tracking enables faster issue resolution.
Chances are if you’re using the Debezium for Oracle connector, you’ve encountered the infamous exception about the SCN could not be found in your transaction logs. In this blog post, we’ll not only talk about what this exception means, but the why, and troubleshooting steps you should take.
The Debezium team has been extremely busy this past quarter as we prepared for this summer release, and we’re excited to announce the immediate availability of Debezium 3.2.0.Final. This release includes a slew of features including integration with OpenLineage, a new Quarkus DevService/GraalVM extension, Qdrant vector database sink support, improvements to Debezium Platform and AI, and much more!
