Skippr Docs

Appearance

When to Choose ClickHouse for CDC Final State ​

May 2026

Choose ClickHouse for CDC final state when its performance profile matters enough that your team is willing to understand ReplacingMergeTree query behavior.

Short Answer ​

Choose ClickHouse for CDC final state when query performance and ClickHouse-native analytics matter enough that your team is comfortable with ReplacingMergeTree semantics and the occasional need for FINAL on fresh data. It is a good fit for teams that know the warehouse will be optimized around ClickHouse behavior rather than around the immediate-read simplicity of MERGE-first systems.

That does not make ClickHouse weaker for CDC. It makes the shape of the trade-off different. Final state converges through versioned rows and background merges, so the team needs to understand when logical correctness is immediate and when query-time FINAL is the safer choice.

Why Teams Struggle with This ​

This destination is a poor fit if the team wants every analyst query to feel like a generic warehouse table with no engine-specific caveats. It is a strong fit when the team values ClickHouse performance enough to learn the merge model instead of fighting it.

  • Choose ClickHouse when performance-oriented analytics outweigh engine-specific query caveats.
  • Choose it when the team can work with ReplacingMergeTree and use FINAL intentionally.
  • Do not choose it if immediate fresh-data simplicity is the top requirement.
  • Do not confuse high throughput with a free pass on replay and query semantics.

How Skippr Handles It ​

Skippr makes the fit legible because the docs say exactly what matters: ReplacingMergeTree for final-state reconciliation, order tokens for version ranking, tombstones for deletes, and FINAL for point-in-time consistency on fresh reads. That is enough to make an informed destination choice.

A concrete example is an internal product analytics team that already uses ClickHouse and wants CDC-fed user event dimension tables in the same platform. If the team is comfortable teaching analysts when FINAL matters for hot data, ClickHouse can be a strong destination fit.

  • Choose it for ClickHouse-native teams that want CDC final state in the same analytical engine.
  • Choose it when performance characteristics matter more than generic warehouse ergonomics.
  • Expect to document when FINAL is required for freshness-sensitive queries.
  • Keep business keys, delete strategy, and recency columns deliberate from the start.

What the First Useful Version Looks Like ​

ClickHouse is the right CDC destination when the team wants ClickHouse on purpose, not by accident.

If that intent is clear, the engine-specific trade-offs become reasonable rather than annoying.