The rows are created in Postgres. The notebooks, dashboards and models that want them run in Databricks. Whatever sits between the two decides how stale the data is, whether an update or a delete ever arrives, and how many systems somebody has to keep alive.
The usual ways to bridge that gap:
Export and load. COPY each table to a cloud bucket, then pick the files up with COPY INTO or Auto Loader . Freshness is hours to daily, and updates and deletes mean full reloads or a merge you write yourself.
Debezium and Kafka, read with Structured Streaming . Changes arrive within seconds. In exchange you operate Kafka, Kafka Connect, Debezium and a running Databricks job, and the merge logic is yours.
Lakeflow Connect . The PostgreSQL connector from Databricks does change data capture (CDC) on Databricks serverless compute, with nothing to host. The rows land in streaming tables governed by Unity Catalog.
This tutorial takes a fourth route.…