DevNation Live: Kafka and Debezium
0 likes2,970 views
How can you avoid inconsistencies between Kafka and the database? Enter change data capture (CDC) and Debezium. By capturing changes from the log files of the database, Debezium gives you both reliable and consistent inter-service messaging via Kafka and instant read-your-own-write semantics for services themselves.
Ad
More Related Content
What's hot (20)
Similar to DevNation Live: Kafka and Debezium (20)
Ad
More from Red Hat Developers (20)
Ad
Recently uploaded (20)
![Download Wondershare Filmora Crack [2025] With Latest](https://cdn.slidesharecdn.com/ss_thumbnails/neo4j-howkgsareshapingthefutureofgenerativeaiatawssummitlondonapril2024-240426125209-2d9db05d-250419-250428115407-a04afffa-thumbnail.jpg?width=560&fit=bounds)
DevNation Live: Kafka and Debezium
- 14. Pattern: Microservice DataPattern: Microservice Data SynchronizationSynchronization Microservice ArchitecturesMicroservice Architectures Propagate data between different services without coupling Each service keeps optimised views locally #Debezium @gunnarmorling Order Item Stock App Local DB Local DB Local DB App App Item ChangesStock Changes
- 15. Source DB (with "Events" table) Kafka Connect Apache Kafka DBZ Order Events Credit Worthiness Check Events Pattern: OutboxPattern: Outbox Avoiding Dual WritesAvoiding Dual Writes #Debezium @gunnarmorling ID Category Type Payload 123 Order OrderCreated { "id" : 123, ... } 456 Order OrderDetailCanceled { "id" : 456, ... } Order Service Shipment Service Customer Service ID Category Type Payload 123 Order OrderCreated { "id" : 123, ... } 456 Order OrderDetail- Canceled { "id" : 456, ... } 789 ... ... ...
- 17. DemoDemo