Skip to content

roadmap.asciidoc

Latest commit

 

History

History
46 lines (37 loc) · 2.88 KB

roadmap.asciidoc

File metadata and controls

46 lines (37 loc) · 2.88 KB

Debezium Roadmap

This page describes the roadmap for upcoming work on Debezium.

Debezium is community-driven and as such the roadmap constantly evolves to reflect the users needs and contributions. You can find a fine-grained list of planned issues and feature requests in our issue tracker, but this page is a good starting point to see where we are going.

This roadmap is subject to changes. Please get in touch if you think anything important is missing on the roadmap.

1.1

  • Provide a Quarkus extension facilitating the application-side part when implementing the outbox pattern

  • Incubating support for IBM DB2

  • Expose topic with transaction events (begin, end)

  • Incubating support for CloudEvents

  • Analyze and fix performance bottlenecks

  • Add SPI for customizing schema and value representation of given columns

  • Provide standalone container for running Debezium without Apache Kafka and Connect

  • Unify more parts of the code base across connectors, e.g. handling of whitelists

  • Relocate Debezium’s Java packages to io.debezium.internal.*, making it apparent that there’s no public Java API/SPI (apart from the embedded connector and the aforementioned one)

Future 1.x releases

  • API/SPI allowing to implement custom connectors on the foundations of Debezium

  • Rebase MySQL and MongoDB connectors to be based on new common framework developed during the work on the Oracle and SQL Server connectors

  • Exploration of creating aggregated events, based on the streams/data from multiple tables, so to enable use cases which need to incorporate data from multiple tables into a single output structure (e.g. an Elasticsearch document containing order and orderline info)

  • Support more messaging backends, e.g. Kinesis, Apache Pulsar etc.

  • Explore and provide building blocks for implementing CQRS architectures based on change data streams

  • Support for Infinispan as a source

  • Allow to propagate custom contextual data in change messages (e.g. the business user doing a certain change)

  • Alternative implementation for the Oracle connector not based on XStream, but e.g. using LogMiner or similar

  • Re-structure DB history topic to have proper semantic representation instead of being DDL-based (DBZ-549)

  • Support for Infinispan as a sink (to enable caching use cases)

  • Provide more detailed monitoring information about Debezium’s internal state and health via JMX (e.g. to spot loss of DB connection while the connector still is running)

  • Explore publication of change events via reactive data streams (on top of embedded connector)

  • DB history topic compaction tool

Past Releases

Please see the releases overview page to learn more about the contents of past Debezium releases.