How Apache Kafka® Generates Value In Retail With Confluent

on YouTube ↗21m

" summary

Shows a concrete migration path from monolith to event-driven microservices using Kafka: use CDC to stream DB changes into a topic for reads, then move writes to the topic while syncing back to the legacy DB, enabling incremental Strangler Fig migration. Claims developer velocity increases, TCO falls, and real-time features (fraud detection, forecasting) run with Confluent Cloud, Schema Registry and ksqlDB. Mentions 120+ connectors, multi-region clusters, infinite storage and durable replay for postmortems.

AI-written summary · about

" chapters (8)

1. 0:00Introduction
2. 2:04Monolithic systems challenges
3. 5:36REST APIs vs messaging queues
4. 9:09Event-driven architecture benefits
5. 11:58Why use Confluent
6. 15:08Common Kafka use cases
7. 16:56Strangler fig pattern explained
8. 20:46Closing and Q&A

" related talks

• 59mBuilding Data Intensive Microservices with Apache KafkaYaniv Rodenski · NDC Sydney 2017
• 33mMicroservices, Events, and Breaking the Data Monolith with KafkaBen Stopford, Cornelia Davis · Cloud Foundry Summit Europe 2019
• 42mCreating event-driven microservices: the why, how and whatKatherine Stanley · Voxxed Days Microservices 2019
• 30mAccelerate Modernization with Confluent and YugabyteDBAnanda Bose, Amey Banarse · Distributed SQL Summit 2022
• 50mMoving from legacy to event-driven with KafkaJeroen van der Gulik · Dutch PHP Conference 2018
• 37mEverything you Wanted to Know about Apache Kafka but you Were too Afraid to Ask!Ricardo Ferreira · Big Data Conference Europe 2019
• 31mEvent driven communication with Kafka on KubernetesRaihan Khan · KCD Dhaka 2024
• 17mOvercome By Events - Apache Kafka And Event-oriented ArchitectureJay Kreps · Big Data LDN 2018