Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Initial draft of 2025 roadmap #1088

Merged
merged 2 commits into from
Jan 6, 2025
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
60 changes: 35 additions & 25 deletions roadmap.asciidoc
Original file line number Diff line number Diff line change
Expand Up @@ -24,41 +24,51 @@ As our engineering capacity is limited, we're focusing our efforts on a single r
i.e. patch releases for the current stable minor release (e.g. 1.2.1.Final) are done in case of critical bug fixes only.
====

== 2.7 - June 2024
== 3.1 - March 2025

* Official MariaDB connector
* Db2 z/OS source connector
* Introduce an SPI to reduce memory footprint for multi-tenant databases with identical schemas
* R&D for read-only incremental snapshots for other relational connectors
* R&D to determine feasibility of using SQL Server transaction logs rather than capture instances
* Design/Implement user-friendly offset manipulation (i.e, start at a specific position in the transaction logs)
* Streaming from MongoDB collections
* Sink connector for MongoDB
* Additional monitoring - Quantimeter
* Expand Oracle 23c support (pending Oracle's EE release of 23c)
* New Debezium UI R&D for integration with Debezium Server and Operator
* Debezium Operator promoted to stable
* Oracle 12c support sunset (best-effort moving forward)
* Completed implementation and refactoring of MongoDB sink connector
* Message vectorization support (via SMT)
* Sink for InstructLab
* Sink for vector databases (TBD)
* Condition-based lifecycle control of Debezium Engine
* Revamped ExtractNewDocument state SMT to handle complex nested documents and arrays
* Support Transformations in Debezium Platform (UI)
* Support signaling in Debezium Platform (UI)
* Make storage configurable at deploy time in Debezium Platform (UI)
* Design Debezium component descriptors / registry

== 3.0 - September 2024
== 3.2 - June 2025

* Java 17 baseline
* Kafka 3.1 minimum baseline support
* Source connector for InfluxDB time series database
* New off-heap Oracle transaction buffer implementations, more details soon.
* Exactly-Once support for other connectors
* Remove deprecated code
* Implement read-only incremental snapshots for relational connectors
* And much more...
* OpenLineage integration
* Debezium Server support for Debezium sink (MongoDB and JDBC) connectors
* Debezium Engine Quarkus integration
* Read-only incremental snapshot for MongoDB
* WebAssembly support in scripting transformations
* Support for two stage processing architecture in Oracle connector
* Design/Implement user-friendly offset manipulation (i.e, start at a specific position in the transaction logs)
* Design/Implement Debezium component descriptors / registry

== 3.1 - December 2024
== 3.3 - September 2025

* Oracle 12c support sunset (best-effort moving forward).
* Create PoC for implementing sagas (long-running business transactions spanning multiple (micro-)services) using CDC and the outbox pattern
* Explore and provide building blocks for implementing CQRS architectures based on change data streams
* Exactly-Once support for other connectors
* Additional monitoring - Quantimeter
* Make storage configurable at runtime in Debezium Platform (UI)

== Future Releases
== 3.4 - December 2025

* Read-only incremental snapshot for SQL Server and Oracle
* Add schema history compaction tool
* Support vaults in Debezium Platform (UI)
* Design upgradability of already configured resources in Debezium Platform (UI)

== Future Releases

* Source connector for InfluxDB time series database
* Introduce an SPI to reduce memory footprint for multi-tenant databases with identical schemas

* Provide a Debezium-specific SPI for describing change event schemas
* API/SPI allowing to implement custom connectors on the foundations of Debezium
* 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)
Expand Down