Skip to content

Commit e4d4dfd

Browse files
committed
Debezium 2026 Survey Results blog: Update what we're doing
Signed-off-by: Chris Cranford <chris@hibernate.org>
1 parent 146f35e commit e4d4dfd

1 file changed

Lines changed: 25 additions & 1 deletion

File tree

_posts/2026-04-14-debezium-2026-survey-results.adoc

Lines changed: 25 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -393,7 +393,31 @@ People find it because they're looking for a solution and it's surfaces well on
393393
The community feedback is extremely valuable to the project team.
394394
Acting on it is what matters, and here's where the survey results are directly influencing our priorities:
395395

396-
TBD
396+
**Documentation**::
397+
We are actively discussing how we can improve our overall website, including the documentation.
398+
This includes providing better troubleshooting and operational guides, managed service setup guides, and improved examples.
399+
We've also heard the feedback about better search, and we are actively exploring options.
400+
We are also integrating documentation directly into the Debezium Platform, providing a better in-context experience.
401+
402+
**Management tooling**::
403+
The demand for a web-based user interface is clear and consistent.
404+
The Debezium Platform is our answer to this, and the survey results reinforce that we need to continue investing in it.
405+
Monitoring and observability, along with guided workflows, are being integrated into the Platform. +
406+
+
407+
Looking further ahead, notifications for incremental snapshots and Kubernetes event dispatching from the Debezium operator are already planned.
408+
We're also exploring CLI-based tooling and host-based deployment options for Debezium Server; nothing to announce just yet, but it's actively being explored, and we hope to have more soon.
409+
410+
**Connector coverage**::
411+
Time-series and vector databases are clearly on the community's mind, and they're on ours too.
412+
Debezium Server source connectors for Milvus and Qdrant are on the roadmap.
413+
A new graph database source connector, a SQLite source connector, and an Elasticsearch sink connector are all planned for later this year.
414+
415+
**Operational improvements**::
416+
Incremental snapshots and observability are both active areas.
417+
Micrometer monitoring via OpenTelemetry is on the roadmap.
418+
Multithreaded single table snapshots were introduced earlier this year to provide scalability for initial and blocking snapshots.
419+
Read-only incremental snapshots for SQL Server and Oracle are planned for a future release.
420+
Dead Letter Queue (DLQ) handling improvements are also on our radar.
397421

398422
== Thank You
399423

0 commit comments

Comments
 (0)