RDBMS and Apache Geode Data Movement
summary
Describes a cloud‑native ETL pipeline that moves relational data into Apache Geode using Spring Cloud Stream with RabbitMQ/Kafka and JDBC readers, splitting work into source/processor/sink microservices. Claims handle huge initial loads by creating synthetic events, processes 60 million records in about six hours, and sustains ~600,000 events per day with 15–20 ms API latency. Shows code, DB trigger/CDC options, batching to Geode, and a dead‑letter retry pattern that proves reliable.
AI-written summary · about
chapters (15)
- 0:00Introduction
- 0:20Shoutouts
- 0:48About HCSC
- 1:31The Problem
- 2:54Simple Extract Transform Load
- 3:55EventDriven Process
- 5:32Microservice Architecture
- 7:17Spring Cloud Stream
- 9:17Demo
- 10:01App Setup
- 11:55Creating Regions
- 23:59Multiple Streams
- 26:10Failed Messages
- 30:21Metrics
- 31:18Outro
related talks
39mRethinking RDBMS Data Migration
45mModern Data Architecture
25mAccelerating Data Processing and Consumption for Building Modern Apps at the Edge
53mBig Data: from mammoth to elephant
31mOne Data Pipeline to Rule Them All
41mApplying Geospatial Analytics at a Massive Scale using Kafka, Spark and Elasticsearch on DC/OS
30mFive Challenges in Real-time Stream Processing and Five Solutions
01h 20mSupercharging Operations and Analytics: Using Spring XD to Support Analytics and CEP
