Real-Time Data Streaming with YugabyteDB CDC and Azure Event Hubs

Real-time data streaming with YugabyteDB CDC and Azure Event Hubs

Stream data from YugabyteDB to Azure Event Hubs using Kafka Connect

The Azure Event Hubs data streaming service is Apache Kafka compatible, enabling existing workloads to easily be moved to Azure. With the Debezium Connector for YugabyteDB, we can stream changes from a YugabyteDB cluster to a Kafka topic using Kafka Connect.

In this tutorial, we'll examine how the YugabyteDB CDC can be used with Azure Event Hubs to stream real-time data for downstream processing.

In the following sections, you will:

  1. Deploy and configure a single-node YugabyteDB cluster.
  2. Configure Azure Event Hubs with an access policy.
  3. Set up Kafka Connect to connect the YugabyteDB CDC to the Event Hubs.
  4. Create an application to insert orders in our database and view the changes downstream.

What you'll build

Find the full project on GitHub. The project uses an eCommerce application and DB schema along with YugabyteDB CDC functionality to send data to Azure Event Hubs via Kafka Connect.

This application runs a Node.js process to insert order records to a YugabyteDB cluster at a regular, configurable interval. The records are then automatically captured and sent to Azure Event Hubs.


Get started with YugabyteDB

With YugabyteDB downloaded on your machine, create a cluster and seed it with data:

  1. Start a single-node cluster using yugabyted.

    ./path/to/bin/yugabyted start 
  2. Connect to the cluster using ysqlsh.

    ./path/to/bin/ysqlsh -U yugabyte
  3. Prepare the database schema.

    CREATE TABLE users (
    id UUID PRIMARY KEY DEFAULT uuid_generate_v4(),
    first_name VARCHAR(255),
    last_name VARCHAR(255)
    CREATE TABLE products (
    id UUID PRIMARY KEY DEFAULT uuid_generate_v4(),
    brand VARCHAR(255),
    model VARCHAR(255)
    CREATE TABLE orders (
    id UUID PRIMARY KEY DEFAULT uuid_generate_v4(),
    user_id UUID REFERENCES users(id),
    product_id UUID REFERENCES products(id),
    quantity INT NOT NULL,
    status VARCHAR(50)
  4. Add users and products to the database.

    users (first_name, last_name)
    ('Gracia', 'Degli Antoni'),
    ('Javier', 'Hiom'),
    ('Minnaminnie', 'Este'),
    ('Hartley', 'Arrow'),
    ('Abbi', 'Gallear'),
    ('Lucila', 'Corden'),
    ('Henrietta', 'Fritschel'),
    ('Greta', 'Gething'),
    ('Raymond', 'Lowin'),
    ('Rufus', 'Gronowe');
    products(brand, model)
    ('hoka one one', 'speedgoat 5'),
    ('hoka one one', 'torrent 2'),
    ('nike', 'vaporfly 3'),
    ('adidas', 'adizero adios pro 3');

Get started on Azure Event Hubs

  1. Create an Azure Event Hubs Namespace in the Azure Web Portal.

    Create Azure Event Hubs Namespace


    The Standard pricing tier is required for Kafka compatibility.


    An Event Hubs instance will be created automatically by Debezium when Kafka Connect is configured. Event Hubs instances can be configured to automatically capture streaming data and store it in Azure Blob storage or Azure Data Lake Store, if desired.

  2. Create a new Shared Access Policy in the Event Hubs Namespace with Manage access. This is a best practice, as opposed to using the root access key for the namespace to securely send and receive events.

    Create a new Shared Access Policy

Configure Kafka Connect

While Kafka's core broker functionality is being replaced by Event Hubs, Kafka Connect can still be used to connect the YugabyteDB CDC to the Event Hubs we just created. The script is used to start Kafka Connect in a distributed mode. This script can be found in the bin directory of the downloaded Kafka distribution.

A Kafka Connect configuration file is required to provide information about the bootstrap servers (in this case, the Event Hubs host), cluster coordination, and data conversion settings, just to name a few. Refer to the official documentation for a sample Kafka Connect configuration for Event Hubs.

  1. Create a Kafka Connect configuration file named event-hubs.config.

    # Event Hubs requires secure communication
    # required EH Kafka security settings
    sasl.mechanism=PLAIN required username="$ConnectionString" password="{YOUR.EVENTHUBS.CONNECTION.STRING}";
    producer.sasl.mechanism=PLAIN required username="$ConnectionString" password="{YOUR.EVENTHUBS.CONNECTION.STRING}";
    consumer.sasl.mechanism=PLAIN required username="$ConnectionString" password="{YOUR.EVENTHUBS.CONNECTION.STRING}";
  2. Replace {YOUR.EVENTHUBS.FQDN} with the Event Hubs Namespace host name.

    Locate domain name for Event Hubs Namespace

  3. Replace {YOUR.EVENTHUBS.CONNECTION.STRING} with an Event Hubs connection string to your namespace.

    Locate connection string

  4. Copy your configuration file to the Kafka bin directory.

    cp /path/to/event-hubs.config  /path/to/kafka_2.12-3.2.0/bin
  5. Copy the Debezium Connector for YugabyteDB to the Kafka libs directory.

    cp /path/to/debezium-connector-yugabytedb-1.9.5.y.15.jar /path/to/kafka_2.12-3.2.0/libs
  6. Run Kafka Connect via the script from the Kafka root directory.

    ./bin/ ./bin/event-hubs.config
  7. Create a CDC stream ID to connect to Kafka Connect.

    ./bin/yb-admin --master_addresses create_change_data_stream ysql.yugabyte
    CDC Stream ID: efb6cd0ed21346e5b0ed4bb69497dfc3
  8. POST a connector for YugabyteDB with the generated CDC stream ID value.

    curl -i -X POST -H "Accept:application/json" -H "Content-Type:application/json" \
    localhost:8083/connectors/ \
    -d '{
    "name": "ybconnector",
    "config": {
        "connector.class": "io.debezium.connector.yugabytedb.YugabyteDBConnector",
        "database.master.addresses": "",
        "database.user": "yugabyte",
        "database.password": "yugabyte",
        "database.dbname" : "yugabyte",
        "": "dbserver1",

Now writes to the orders table in the YugabyteDB cluster will be streamed to Azure Event Hubs via Kafka Connect.


Debezium will auto-create a topic for each table included and several metadata topics. A Kafka topic corresponds to an Event Hubs instance. For more information, check out the Kafka and Event Hubs conceptual mapping.

Test the application

We can test this real-time functionality by running a sample application to insert orders into our YugabyteDB instance. With a Kafka Connect configured properly to an Event Hubs namespace, we can see messages being sent to an Event Hubs instance.

  1. Clone the repository.

    git clone
    cd yugabytedb-azure-event-hubs-demo-nodejs
  2. Install Node.js application dependencies.

    npm install
  3. Review the Node.js sample application.

    const { Pool } = require("@yugabytedb/pg");
    const pool = new Pool({
        user: "yugabyte",
        host: "",
        database: "yugabyte",
        password: "yugabyte",
        port: 5433,
        max: 10,
        idleTimeoutMillis: 0,
    async function start() {
        const usersResponse = await pool.query("SELECT * from users;");
        const users = usersResponse?.rows;
        const productsResponse = await pool.query("SELECT * from products;");
        const products = productsResponse?.rows;
        setInterval(async () => {
            try {
                const randomUser = users[Math.floor(Math.random() * users.length)];
                const randomProduct =
                products[Math.floor(Math.random() * products.length)];
                const insertResponse = await pool.query(
                "INSERT INTO orders(user_id, product_id, quantity, status) VALUES ($1, $2, $3, $4) RETURNING *",
                [randomUser?.id, randomProduct?.id, 1, "processing"]
                console.log("Insert Response: ", insertResponse?.rows?.[0]);
            } catch (e) {
                console.log(`Error while inserting order: ${e}`);
        }, process.env.INSERT_FREQUENCY_MS || 50);

    This application initializes a connection pool to connect to the YugabyteDB cluster using the YugabyteDB node-postgres smart driver. It then randomly inserts records into the orders table at a regular interval.

  4. Run the application.

    node index.js 

    The terminal window will begin outputting the response from YugabyteDB, indicating that the records are being inserted into the database.

    # Example output
    Insert Response:  {
        id: '6b0dffe9-eea4-4997-a8bd-3e84e58dc4e5',
        user_id: '17246d85-a403-4aec-be83-1dd2c5d57dbb',
        product_id: 'a326aaa4-a343-45f6-b99a-d16f6ac7ad14',
        order_date: 2023-12-06T19:54:25.313Z,
        quantity: 1,
        status: 'processing'
    Insert Response:  {
        id: '29ae786e-cc4d-4bf3-b64c-37825ee5b5a7',
        user_id: '7170de37-1a9f-40de-9275-38924ddec05d',
        product_id: '7354f2c3-341b-4851-a01a-e0b3b4f3c172',
        order_date: 2023-12-06T19:54:25.364Z,
        quantity: 1,
        status: 'processing'

    Heading over to the Azure Event Hubs instance database1.public.orders, we can see that the messages are reaching Azure and can be consumed by downstream applications and services.

    Incoming messages


YugabyteDB CDC combined with Azure Event Hubs enables real-time application development using a familiar Kafka interface.

If you're interested in real-time data processing on Azure, check out Azure Synapse Analytics integration using Azure Event Hubs.