How deeply does Kafka Streams in Action, Second Edition cover change-data-capture?

Explains captured operations, Kafka-topic storage, connector configuration, and the distinction between custom clients and production-ready connectors.

Change-data-capture

As explained in Kafka Streams in Action, Second Edition

Change data capture is a technique for detecting and exporting database record changes such as inserts, updates, and deletes as they occur.

Change data capture (CDC) detects database-table changes and exports INSERT, UPDATE, and DELETE events to other applications. Kafka Connect stores those changes in a Kafka topic, making them available to downstream consumers with low latency while leaving the existing application unchanged. section 5.1

A CDC integration typically involves:

A database table whose changes are captured as they occur. section 5.1
A Kafka Connect connector configured as a plugin through a JSON configuration file. section 5.1
A Kafka topic that stores the exported changes for downstream consumers. section 5.1

Capturing table changes

A connector captures INSERT, UPDATE, and DELETE operations from a relational database and writes them to Kafka. Other applications consume the resulting events without requiring changes to the legacy application. section 5.1

How Kafka Streams in Action, Second Edition covers it

Cover of Kafka Streams in Action, Second Edition

liveBook manning.com

Read Kafka Streams in Action, Second Edition on liveBook Get the book at manning.com

Also explained in

liveBook manning.com

Apache Kafka in ActionChange data capture is a technique that monitors and records changes made to a data source rather than repeatedly reading its complete current contents.
liveBook manning.com

ScyllaDB in ActionChange data capture is a database feature that records table mutations in a change-log table so they can be consumed over time.
liveBook manning.com

Kafka for ArchitectsChange data capture is a pattern that observes a source system's change records and emits insertions, updates, and deletions as events.
liveBook manning.com

Architecting an Apache Iceberg LakehouseChange data capture processing handles records representing inserts, updates, and deletes made to a source system.

Compare how 5 books explain change-data-capture →

Related concepts

transaction loguses · A transaction log is an ordered record of transactions, transaction-related events, or resulting data changes, maintained as a history and often used for tracking or recovery.
CDC tableproduces · A CDC table is a ScyllaDB table that stores records describing changes made to rows in a corresponding source table.
database tableuses · A database table is a relational database structure that organizes records into rows and defined columns.
Apache Kafkaused by · Apache Kafka is a distributed event-streaming platform for publishing, storing, processing, and consuming streams of records.
small fileproduces · A small file is a data file whose size is sufficiently low that file-management, metadata, and scheduling overhead become significant relative to its data content.
Debeziumused by · Debezium is an open-source change data capture platform that captures database changes and streams them to downstream systems.

This explainer was generated by Manning's knowledge graph from the text of Kafka Streams in Action, Second Edition. The section links point to the parts of the book it draws on.