Data Cartography
summary
Claims a practical method: a four-step design paradigm that picks storage top-down from operation → application → data model → data store. Shows when row SQL is fine and when graph DBs (native vs non-native) cut runtime joins by design, demonstrates using hub-and-spoke and betweenness centrality for routing, and explains consensus needs solved with hash graph (gossip protocol) or blockchain when operation requires Byzantine fault tolerance.
AI-written summary · about
chapters (6)
- 0:00Start
- 2:54SPOKE - HUB MODEL: APPLICATIONS
- 5:13MAPPING THE DATA LANDSCAPE
- 5:37DATA MODEL
- 8:47GRAPH DATABASE IMPLEMENTATION
- 12:04BYZANTINE GENERALS PROBLEM
related talks
27mThe Evolution of Data Architecture
01h 01mData-Centric in Action
29mCartography: using graphs to improve and scale security decision-making
31mData Unleashed: A Developer's Perspective on Navigating the Architecture Maze
58mUnderstanding Big Data for Software Engineers
19mUnraveling the Web of Relationships: Understanding Graph Data
18mGermany's Next Top Data Model
37mKEYNOTE: Data Architecture Turned Upside Down