Spell of Transmutation - Using Debezium to Transfer Realtime Data Changes to Event Hub
summary
Sets up Debezium to stream SQL Server CDC into Azure Event Hub using an Azure Container Instance that posts via the Kafka endpoint; includes a local Azure Function and Stream Analytics consumer. Covers exact config choices: snapshot mode vs initial, need for a persistent history store, disabling tombstones on delete false, and SQL firewall/Kafka gotchas. Warns container constantly polls (so serverless SQL wakes and costs spike). Demos are recorded and show inserts flowing end-to-end.
AI-written summary · about
chapters (13)
- 0:00Introduction to Debezium
- 4:44Why use near real-time
- 6:46Understanding the components
- 11:34Getting started with Debezium
- 14:21Preparing the SQL database
- 18:48Setting up the event hub
- 23:50Deploying the container
- 27:25Configuring the connector
- 31:19Connector gotchas and tips
- 36:05Verifying and debugging
- 37:43Consuming the data stream
- 40:18Using stream analytics
- 43:15Conclusion and best practices
related talks
01h 11mChange data capture pipelines with Debezium and Kafka Streams
30mChange Data Capture With Flink SQL And Debezium
26mDebezium Server - New CDC runtime on the horizon!
48mStreaming Database Changes with Debezium
31mChange Data Capture for non relational databases
27mUnderstanding stream table duality using Kafka, Flink SQL and Debezium format
47mBuilding highly scalable IoT streaming solutions using Azure Event Hubs and MongoDB
43mImplement a Serverless Data Platform with Microsoft Azure
