Push-based CDC into Unity Catalog with Zerobus Ingest and Debezium

Databricks has published guidance on moving change data capture (CDC) from operational databases into Unity Catalog by combining Zerobus Ingest with Debezium. Debezium is an established open-source connector family that reads database transaction logs and emits row-level change events; Zerobus Ingest is presented as the path for pushing those events into Unity Catalog, the catalogue layer that governs tables and access in the Databricks platform.
The practical point is the direction of travel: database changes are pushed into Unity Catalog tables as they happen, instead of being pulled in on a scheduled batch. This suggests a lower-latency route from operational systems into analytical tables, though the material does not specify supported database engines, latency figures, throughput, pricing or availability.
For teams already running Debezium, the pattern keeps the familiar capture layer and changes where the events land. In practice, streaming CDC requires attention to ordering, deletes, schema evolution and exactly-once handling, and those concerns should be validated before production use.
Why it matters: teams feeding Unity Catalog from transactional databases are the audience, and the combination points to fresher tables and less custom pipeline glue. Developers should confirm engine support and operational limits with Databricks before designing around it, since those details are not stated here.
Based on reporting from the original publisher. Visit the source for full context and later updates.
Publisher excerpt
Data in operational databases drives business decisions, and much of that analysis...