Accelerate Modernization with Confluent and YugabyteDB
summary
Shows how Confluent (Kafka), YugabyteDB and connectors implement CDC into Kafka to decouple legacy DB2 mainframes, move reads first then writes over 6–9 months, and serve microservices with a Postgres-compatible API and Cassandra API. Demonstrates a real migration that cuts end‑of‑day processing from 8–10h to 2–3h, eliminates duplicate-data bottlenecks, supports elastic CKU scaling for peak events, uses Schema Registry for governance, and achieves multi‑region resilience with near‑zero data loss.
AI-written summary · about
chapters (13)
- 0:00Introduction
- 4:55Decouple dependencies
- 6:33Data internships
- 8:45What is Confluent
- 10:10What is YugabyteDB
- 12:37YugabyteDB Kafka Connect
- 13:52Confluent
- 15:14Governance
- 18:18Ecosystem
- 20:19Scale
- 23:30YugabyteDB
- 24:41Case Study
- 28:58Closing Thoughts
related talks
18mData Modernization Using Confluent and Yugabyte
31mMake it Painless: YugabyteDB Database Migration Solutions
21mHow Apache Kafka® Generates Value In Retail With Confluent
39mDeep Dive on Using YugabyteDB's Change Data Capture Connector
37mDatabase Modernization at Cloud Scale: Minimizing Risk and Disruption
30mChange Data Streaming Patterns in Distributed Systems
02h 03mBuild CDC pipeline using Kafka ecosystem
35mScaling UPI for the Future: Zero Downtime Migration to