Skip to content

Debezium 2026 Survey Results blog#1248

Merged
Naros merged 10 commits intodebezium:developfrom
Naros:2026-survey-results
Apr 27, 2026
Merged

Debezium 2026 Survey Results blog#1248
Naros merged 10 commits intodebezium:developfrom
Naros:2026-survey-results

Conversation

@Naros
Copy link
Copy Markdown
Member

@Naros Naros commented Apr 14, 2026

No description provided.

@github-actions
Copy link
Copy Markdown

github-actions Bot commented Apr 14, 2026

🎊 PR Preview has been successfully built and deployed to https://debezium-debezium-github-io-preview-pr-1248.surge.sh

Comment thread _posts/2026-04-14-debezium-2026-survey-results.adoc Outdated
Comment thread _posts/2026-04-14-debezium-2026-survey-results.adoc Outdated
@mfvitale
Copy link
Copy Markdown
Member

mfvitale commented Apr 15, 2026

@Naros nice read! I left a minor comment but overall it LGTM.

Copy link
Copy Markdown
Member

@vjuranek vjuranek left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Nice read! The only thing I'm missing is to mention absolute number of responses. If it's intentionally not provided, then it should be removed from the third picture ("Switched away 3 out of 69")

@Naros
Copy link
Copy Markdown
Member Author

Naros commented Apr 15, 2026

The only thing I'm missing is to mention absolute number of responses. If it's intentionally not provided, then it should be removed from the third picture ("Switched away 3 out of 69")

@vjuranek, that's a good point, and one I'm not really sold on how best to convey that.

On the one hand, I could imagine some who would like to know the actual number of respondents. On the other hand, I could imagine that knowing the actual number could evoke mixed feelings about the sample size. For this reason, I was actually considering converting that metric to a percentage, as I think 0.04% looks better, and it also aligns that with the other chart representations.

What does everyone think about that?

@jpechane
Copy link
Copy Markdown
Contributor

@Naros Percentage is fine but if you don't want to make any assumptions on sample size then you should probably replace the term dozens at the beginning of article with numerous.

Comment thread _posts/2026-04-14-debezium-2026-survey-results.adoc Outdated
The scale at which people are running Debezium is worth pausing on.
When we asked about change throughput, responses ranged from as low as 1-25 changes per minute up to 1-2 million changes per minute.
Many environments operate in the tens or hundreds of thousands per minute.
Some PostgreSQL environments see technical commit counts up to 19k per minute during peak transaction loads.
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can we have a chart that would create buckets of traffic and correlate it with theprecentage of respondents.

Comment thread _posts/2026-04-14-debezium-2026-survey-results.adoc Outdated
Comment thread _posts/2026-04-14-debezium-2026-survey-results.adoc Outdated
@Naros Naros marked this pull request as ready for review April 21, 2026 05:50
@Naros Naros force-pushed the 2026-survey-results branch from e4d4dfd to e2f8519 Compare April 21, 2026 05:51
Naros added 9 commits April 21, 2026 03:14
Signed-off-by: Chris Cranford <chris@hibernate.org>
Signed-off-by: Chris Cranford <chris@hibernate.org>
Signed-off-by: Chris Cranford <chris@hibernate.org>
Signed-off-by: Chris Cranford <chris@hibernate.org>
Signed-off-by: Chris Cranford <chris@hibernate.org>
Signed-off-by: Chris Cranford <chris@hibernate.org>
Signed-off-by: Chris Cranford <chris@hibernate.org>
Signed-off-by: Chris Cranford <chris@hibernate.org>
Signed-off-by: Chris Cranford <chris@hibernate.org>
@Naros Naros force-pushed the 2026-survey-results branch from eaf8ac0 to b9549a0 Compare April 21, 2026 07:15
Copy link
Copy Markdown
Member

@vjuranek vjuranek left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

Copy link
Copy Markdown
Member

@gunnarmorling gunnarmorling left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

That's awesome, so many great insights in that one!

A few comments/suggestions inline.

</style>
++++

Earlier this year, we asked the Debezium community to tell us how they're using the project, what's working, and where we need to do better.
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
Earlier this year, we asked the Debezium community to tell us how they're using the project, what's working, and where we need to do better.
Earlier this year, we [asked the Debezium community](link?) to tell us how they're using the project, what's working, and where we need to do better.

Comment thread _posts/2026-04-21-debezium-2026-survey-results.adoc Outdated
++++

Additionally, **98.6% of respondents** are currently using Debezium or plan to within the next year.
Of those currently using it, 91.3% are active users.
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

What does that mean? How can one be currently using it, but not actively?

Additionally, **98.6% of respondents** are currently using Debezium or plan to within the next year.
Of those currently using it, 91.3% are active users.
Only three respondents had switched to other solutions.
For an open-source project competing against well-funded commercial alternatives, that retention is remarkable.
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

That feels a bit misleading, I mean it's not as if Debezium isn't commercially funded?

Copy link
Copy Markdown
Member Author

@Naros Naros Apr 22, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

That's true, I suppose my framing here needs work. It might be better to avoid the comparison here and just stick to the retention positive aspect.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@Naros I think the sentence can stay, just drop competing against well-funded commercial alternatives.

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I wordsmithed it a bit and I think this frames the intent better:

Additionally, Debezium's adoption numbers tell a compelling story: nearly all respondents (98.6%), are either actively using it or plan to within the next year, with 91.3% of those already in active use today.
With only 4.3% of respondents having moved to a competing solution or no longer needing a CDC at all, the retention speaks for itself.

</div>
++++

When we asked about change throughput, responses ranged from as low as 1-25 changes per minute up to 1-2 million changes per minute.
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is that change events, or transactions (with multiple events)? If it's the former, I'd have expected much higher numbers, actually. We know folks use Debezium for emitting hundreds of thousands of events per sec. Nobody in the survey reporting that scale? If so, it would be worth to drop somewhere that Debezium scales beyond those numbers.

Copy link
Copy Markdown
Member Author

@Naros Naros Apr 22, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We asked for changes per minute.

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Gotcha. In general, I think xyz/sec is the better metric; it's established and lets people honestly compare.

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Understood.


When we asked about change throughput, responses ranged from as low as 1-25 changes per minute up to 1-2 million changes per minute.
Many environments operate in the tens or hundreds of thousands per minute.
Some PostgreSQL environments see technical commit counts up to 19k per minute during peak transaction loads.
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

What is "technical commit count"?

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

An auto-correct mistake. That should likely just be "commit counts".

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I removed it as I don't think it provides much value to this section, as the updated section I think is clear and concise. Let me know what you think, @gunnarmorling.

Signed-off-by: Chris Cranford <chris@hibernate.org>
@Naros
Copy link
Copy Markdown
Member Author

Naros commented Apr 24, 2026

@gunnarmorling from your PoV, is this g2g?

@gunnarmorling
Copy link
Copy Markdown
Member

Yepp, LGTM. Great stuff!

@Naros Naros merged commit 8d632a1 into debezium:develop Apr 27, 2026
4 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants