Featured Posts

Tags
apache kafka apache kafka apicurio avro aws batch caassandra camel cassandra cdc channels community community stories connectors containers cqrs custom datalake db2 ddd debezium debezium server debezium ui deduplication discussion docker elasticsearch event sourcing exactly once semantics example examples features fedora flink hiring ibmi iceberg informix integration introduction jaeger jdbc json kafka kafka streams kafka streams kogito ksql kubernetes lakehouse machine learning mariadb microservices mongo mongodb mysql news newsletter notifications online learning operator oracle outbox performance postgres presentation production quarkus questdb rds releases schema scylla secrets sentry serialization signaling smt snapshots spanner spark sql sqlserver tensorflow testcontainers tests time series timescaledb topics tracing transactions vagrant vitess website

On behalf of the Debezium community it’s my great pleasure to announce the release of Debezium 0.10.0.Final!

As you’d expect it, there were not many changes since last week’s CR2, one exception being a performance fix for the pgoutput plug-in of the Postgres connector, which may have suffered from slow processing when dealing with many small transactions in a short period of time (DBZ-1515).

This release finalizes the work of overall eight preview releases. We have discussed the new features and changes in depth in earlier announcements, but here are some highlights of Debezium 0.10:

In addition, we also removed some previously deprecated options and did some clean-up of the message structures produced by the Debezium connectors, e.g. in regards to certain type mappings. When upgrading from earlier releases, please make sure to carefully study the release notes, which discuss in detail any changed or removed functionality, as well as options which for instance allow to keep the original source structure for some time.

Pleas refer to the orignal announcements for more details (Alpha1, Alpha2, Beta1, Beta2, Beta3, Beta4, CR1, CR2). Altogether, a whopping 171 issues were resolved in Debezium 0.10.

Such effort would not nearly be possible without all the fantastic people in the Debezium community. Until today, almost 130 people have contributed to the main Debezium code repository, plus some more to the incubator and container image repositories. But submitting pull requests with code changes is not the only way to help, we’re equally thankful for each bug report, feature request, suggestions in the chat rooms etc.

Another great thing to observe is the growing number of blog posts, conference presentations and other material covering Debezium in one way or another. We maintain a list of Debezium-related resources on the website; if you know of other contents which should be linked there, please file a PR for adding it.

I can’t begin to express how lucky we feel about all these amazing contributions, no matter whether small or large!

Coming Next: Debezium 1.0!

With Debezium 0.10.0.Final being done, the question is: what’s next? If you thought 0.11, then we got to disappoint you — we’re finally setting course towards Debezium 1.0!

With all the community feedback we got (in parts from huge deployments with hundreds of Debezium connectors), and with the clean-up changes done for 0.10, we feel that it’s finally about time for the 1.0 release and the even increased expectations towards it in regards to compatibility and stability.

We don’t expect many new functionality for 1.0 in comparison over 0.10 (with exception of the incubating connectors), the focus will primarily be on further bug fixing, stability and usability improvements. In the good old tradition of open source, we don’t specify any timeline other than "it’s done, when it’s done". But it should be safe to say that it will be done quicker than 0.10: going forward, we’d like to increase the release cadence and publish new minor releases more often, for sure doing less than eight preview releases as in 0.10. Any contributions, input on the roadmap and other feedback will be very welcomed of course.

Upwards and onwards!

Gunnar Morling

Gunnar is a software engineer at Decodable and an open-source enthusiast by heart. He has been the project lead of Debezium over many years. Gunnar has created open-source projects like kcctl, JfrUnit, and MapStruct, and is the spec lead for Bean Validation 2.0 (JSR 380). He’s based in Hamburg, Germany.

   

About Debezium

Debezium is an open source distributed platform that turns your existing databases into event streams, so applications can see and respond almost instantly to each committed row-level change in the databases. Debezium is built on top of Kafka and provides Kafka Connect compatible connectors that monitor specific database management systems. Debezium records the history of data changes in Kafka logs, so your application can be stopped and restarted at any time and can easily consume all of the events it missed while it was not running, ensuring that all events are processed correctly and completely. Debezium is open source under the Apache License, Version 2.0.

Get involved

We hope you find Debezium interesting and useful, and want to give it a try. Follow us on Twitter @debezium, chat with us on Zulip, or join our mailing list to talk with the community. All of the code is open source on GitHub, so build the code locally and help us improve ours existing connectors and add even more connectors. If you find problems or have ideas how we can improve Debezium, please let us know or log an issue.