Skip to content

Latest commit

 

History

History
 
 

kinesis

Folders and files

NameName
Last commit message
Last commit date

parent directory

..
src/main
src/main
 
 
README.md
README.md
 
 
pom.xml
pom.xml
 
 

README.md

Streaming Database Changes to Amazon Kinesis Using Debezium

Debezium allows to capture and stream change events from multiple databases such as MySQL and Postgres and is mostly used with Apache Kafka as the underlying messaging infrastructure.

Using Debezium's embedded mode it is possible though to stream database changes to arbitrary destinations and thus not be limited to Kafka as the only broker. This demo shows how to stream changes from MySQL database running on a local machine to an Amazon Kinesis stream.

Note: Kinesis is a commercial service by Amazon, running this example will cost you some money. We recommend you remove all resources created for this example afterwards to avoid unnecessary cost.

Prerequisites

  • Java 8 development environment
  • Local Docker installation to run the source database
  • an Amazon AWS account
  • The AWS CLI client
  • jq 1.6 installed

Running the Demo

Starting the MySQL Source Database

We will start a pre-populated MySQL database that is the same as used by the Debezium tutorial:

docker run -it --rm --name mysql -p 3306:3306 -e MYSQL_ROOT_PASSWORD=debezium -e MYSQL_USER=mysqluser -e MYSQL_PASSWORD=mysqlpw quay.io/debezium/example-mysql:2.1

Preparing the CLI environment

It is assumed that you have already executed aws configure as described in AWS CLI getting started guide.

Creating the Kinesis Stream

aws kinesis create-stream --stream-name kinesis.inventory.customers --shard-count 1

You can use an arbitrary number of shards. To keep things simple we capture only one table - customers from the inventory database, so we need only one stream. If you want to capture multiple tables you need to create the equivalent streams for them too. The naming scheme of streams is <engine_name>.<database_name>.<table_name> which in our case is kinesis.inventory.<table_name>.

Creating a Stream Iterator

We will use AWS CLI to read messages.

ITERATOR=$(aws kinesis get-shard-iterator --stream-name kinesis.inventory.customers --shard-id 0 --shard-iterator-type TRIM_HORIZON | jq '.ShardIterator')

Connecting the Database to Kinesis

Start the application that uses Debezium Embedded to get change events from database to Kinesis stream.

mvn exec:java

Reading Events From the Kinesis Stream

Execute this command to obtain the records from the topic using the iterator and print the change event contents:

aws kinesis get-records --shard-iterator $ITERATOR | jq -r '.Records[].Data | @base64d' | jq .

This will return a sequence of JSON messages like this:

{
  "before": null,
  "after": {
    "id": 1001,
    "first_name": "Sally",
    "last_name": "Thomas",
    "email": "sally.thomas@acme.com"
  },
  "source": {
    "version": "2.1.3.Final",
    "name": "kinesis",
    "server_id": 0,
    "ts_sec": 0,
    "gtid": null,
    "file": "mysql-bin.000003",
    "pos": 154,
    "row": 0,
    "snapshot": true,
    "thread": null,
    "db": "inventory",
    "table": "customers"
  },
  "op": "c",
  "ts_ms": 1520513267424
}
{
  "before": null,
  "after": {
    "id": 1002,
    "first_name": "George",
    "last_name": "Bailey",
    "email": "gbailey@foobar.com"
  },
  "source": {
    "version": "2.1.3.Final",
    "name": "kinesis",
    "server_id": 0,
    "ts_sec": 0,
    "gtid": null,
    "file": "mysql-bin.000003",
    "pos": 154,
    "row": 0,
    "snapshot": true,
    "thread": null,
    "db": "inventory",
    "table": "customers"
  },
  "op": "c",
  "ts_ms": 1520513267424
}
...

Updating Records in the Database

Now update a record in the database:

docker run -it --rm --name mysqlterm --link mysql --rm mysql:5.7 sh -c 'exec mysql -h"$MYSQL_PORT_3306_TCP_ADDR" -P"$MYSQL_PORT_3306_TCP_PORT" -uroot -p"$MYSQL_ENV_MYSQL_ROOT_PASSWORD"'

use inventory;
update customers set first_name = 'Sarah' where id = 1001;

If you query the Kinesis stream iterator again, you'll see an update event corresponding to this change.

Deleting the Kinesis Stream

aws kinesis delete-stream --stream-name kinesis.inventory.customers