Data Modernization Using Confluent and Yugabyte
summary
Shows a concrete pattern: capture change streams from legacy sources using Confluent CDC connectors, process events with kstreams/ksql to enrich and materialize views, then persist into Yugabyte for distributed SQL serving. Claims include faster delivery (KeyBank reports multi-month projects shrink), operational durability via zero‑loss across AZs and elastic storage to S3, and a large ecosystem with 120+ connectors. Demonstrates replacing MQ/REST meshes with event-first pub/sub and materialized state in Yugabyte for low-latency microservices.
AI-written summary · about
chapters (11)
- 0:00Introduction
- 1:50Faster app development tenets
- 3:15Monolithic architecture challenges
- 5:22Breaking data monolith
- 7:49Confluent and Yugabyte
- 9:53Yugabyte cloud-native features
- 11:17Confluent streaming benefits
- 13:42Hybrid architecture with linking
- 14:46Real-world connector integration
- 16:10Confluent and Yugabyte demo
- 17:36Q&A
related talks
30mAccelerate Modernization with Confluent and YugabyteDB
22mChange Data Capture: Exploring YugabyteDB’s Modern Design
39mDeep Dive on Using YugabyteDB's Change Data Capture Connector
30mChange Data Streaming Patterns in Distributed Systems
39mModern Event-driven Architecture: Adopting Data in Motion
31mMake it Painless: YugabyteDB Database Migration Solutions
28mDisrupting the Status Quo with Distributed SQL to Deliver Data-Driven Solutions
43mBack to fundamentals: from databases to event-driven platforms
