ClickHouse is where the heavy questions go: the scans and group-bys you would rather not run on the Postgres that takes your orders. The rows are still written in Postgres, so something has to carry every insert, update and delete across. That something decides how stale the numbers are and how many services you keep alive.
The common ways to get from Postgres to ClickHouse:
ClickPipes for Postgres . Change data capture (CDC) through logical replication into ReplacingMergeTree tables, with nothing to host. ClickHouse Cloud only, billed per ClickPipe.
PeerDB , self-hosted. The same approach on a ClickHouse you operate. You run PeerDB, Temporal and a Postgres database for PeerDB's own state.
Debezium, Kafka and the ClickHouse Kafka engine. Changes arrive within seconds. You operate Kafka, Kafka Connect and Debezium, keep a materialized view per table, and write the merge logic for updates and deletes yourself.
Managed extract, load, transform (ELT) tools such as Fivetran, Estuary or Airbyte Cloud.…