perf(bridge): Q1.3 ClickHouse-only batch apply#178
Merged
Conversation
Production bridge path applies events via apply_serving_batch: multi-row orders_v2 and pipeline_events inserts, users_enriched once per unique user, journal last for replay safety. DuckDB is demo/unit only — never opened when the ClickHouse sink is set.
DORA Metrics
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Q1.3 write-path: production serving bridge is ClickHouse only.
apply_serving_batch— multi-roworders_v2+pipeline_eventsusers_enrichedrecompute once per unique user (not per order)Why DuckDB appeared before
Historical dual-write: bridge reused
_process_eventwhich always wrote a local lake then mirrored to CH. That scratch lake was never the API store. Q1.2 skipped it; Q1.3 batches pure CH writes.Verify
Test plan