Modern Data Architecture
summary
Argues that enterprises move from slow nightly ETL data warehouses to a mix of a data lake on Hadoop, a lambda-style batch+speed path and a streaming pipelined replication layer, using CDC change data capture + queues so 4 TB/day sources replicate to Hadoop and an MPP like Greenplum, cutting time‑to‑insight from days (7 days for DR, backups taking days on 10–15 TB) to near real time. Describes concrete stack options: Spring Cloud Data Flow, Kafka/RabbitMQ, Spark, GemFire; pipelining with replayable queues solves DR and ordering limits CDC coverage.
AI-written summary · about
chapters (9)
- 0:00Introduction and speaker background
- 2:35Evolution of data processing systems
- 8:53Traditional data warehouse challenges
- 13:29Moving from ETL to ELT and CDC
- 17:49Introducing data lake and lambda architecture
- 22:29How lambda architecture works
- 27:33Pipelining for real-time replication
- 33:18Technologies for modern data architecture
- 35:51Summary and Q&A start
related talks
34mTales of Data Architecture Evolution
41mModern Data Architectures – What They Are and How to Implement?
25mRemove Slow, Expensive ETL & Bring Data To The Data Lake For Lower Cost, More Performant Analytics
01h 03mReinvente su estrategia de datos con Lagos de Datos Transaccionales
10mData Rivers — The New Analytics Architecture
53mBig Data: from mammoth to elephant
49mData Platform Architecture, Evolution, and Philosophy
29mData Mesh Streaming Patterns: A Real-time Perspective
