liveBook · Manning

Change feed

As explained in Kafka for Architects

A change feed is an ordered stream of records describing changes made to data in a source system.

A change feed is an ordered stream of records describing updates in a source system. In an event-driven architecture, Kafka distributes these changes so services such as Customer360Service can react without synchronous requests. section 5.1.1

Kafka can retain and replay change records, but it is not a database: append-only sequential access does not provide referential integrity, strong consistency, secondary indexes, or full SQL querying. Keep the system of record or read store in a database, and plan retention, compaction, and rebuild latency. section 5.1.1

Profile changes for Customer360Service

ProfileService publishes notifications through Kafka whenever profile data changes. Customer360Service consumes the feed and can reconstruct state by replaying retained events, while a database remains the system of record. section 5.1.1

How Kafka for Architects covers it

How deep it goes
Explains replay, retention, compaction, and rebuild trade-offs, but stops short of implementation details.
Examples
Uses profile notifications, Customer360Service state reconstruction, and compacted Kafka topics as concrete examples.
What you can do after
Evaluate whether Kafka should distribute changes while preserving a database system of record and planning retention costs.
How it connects
Connects change feeds with Kafka, event-driven microservices, databases, synchronous request-response, and shared databases.
Cover of Kafka for Architects
liveBookmanning.com
Read Kafka for Architects on liveBook Get the book at manning.com

This explainer was generated by Manning's knowledge graph from the text of Kafka for Architects. The section links point to the parts of the book it draws on.