Data Unleashed: A Developer's Perspective on Navigating the Architecture Maze
summary
Compares concrete architectures: starting from a single relational database through a data warehouse and lakehouse to a data mesh, with the plumbing named — ETL/ELT, streaming hubs, telemetry and lineage — and concrete tradeoffs: expect months not years to deliver, aim for ~10× ROI or don’t rearchitect, accept a few data copies early, watch cloud compute costs and latency, and one rental car case shows predictive maintenance and live telemetry improve utilization and actually work.
AI-written summary · about
chapters (12)
- 0:00Introduction
- 1:08Data holds real business value
- 3:36Speed, accuracy, insights access
- 7:52Core data architecture components
- 11:26Evaluating database architectures
- 14:16Data warehouse adoption
- 16:27Data lake challenges
- 19:42Lake house pattern
- 21:06Data mesh
- 22:30Data architecture evolution
- 27:48Sustainable data platform principles
- 30:39Cloud cost monitoring & AI
related talks
56mData Unleashed: A Developer's Perspective on Navigating the Architecture Maze
41mModern Data Architectures – What They Are and How to Implement?
58mTales of Data Architecture Evolution
43mAnalytics capabilities architectural patterns: A journey for data-driven insights
25mPlatform Engineering for Modern Data Infrastructure
27mThe Evolution of Data Architecture
58mUnderstanding Big Data for Software Engineers
31mData Warehouses Meet Data Lakes