Tangram: Bridging Immutable and Mutable Abstractions for Distributed Data Analytics
Talkat USENIX ATC '19 · on Wednesday, 2019-07-10· at 14:40· USENIX ATC Track II: Grand Ballroom VII–IX·
summary
Tangram implements MapUpdate to infer whether collections are mutable or immutable and lets update functions perform in-place, key-value updates while map functions remain functional. The system uses partition-based progress control and a bounded-delay synchronous model, plus context-aware failure recovery that distinguishes local vs global failures and either reloads immutable partitions or rolls back mutable partitions to the latest checkpoint. Implemented on 20 machines, Tangram matches specialized systems on bulk, graph, and iterative ML tasks and avoids costly pipeline checkpointing and cross-system data IO.
AI-written summary · about
chapters (9)
- 0:00Introduction
- 0:50Immutable vs Mutable
- 3:24Map Updates
- 8:07Map Updates Implementation
- 11:36Experiments
- 12:14Local failure recovery
- 12:55Global failure recovery
- 14:00Pipeline workload scenario
- 14:55Conclusion
related talks
12mTEGRA: Efficient Ad-Hoc Analytics on Evolving Graphs
50mImmutable Values in the Big Wide World
39mEventually Consistent Data Structures
21mUpdate on Raku Persistent Data Structures
15mTreebeard: A Scalable and Fault Tolerant ORAM Datastore
26mCan we do better than git s Merkle DAG?
38mLost in Transduction
11mBig Data Analytics: Immutability & Idempotence
