Structured Data at Box: How We're Building for Scale
summary
Covers Box’s MySQL-based sharded database and caching architecture for serving hundreds of thousands of businesses and tens of millions of users. Describes specific design choices made in that sharded setup and evaluates how those choices have worked out for Box at scale.
AI-written summary · about
chapters (13)
- 0:00Intro
- 2:57Core Application Data Architecture
- 3:48Cache usage at Box
- 4:27Cache Pool Stats
- 5:41Direct client access is a problem...
- 7:55Tron Architecture
- 9:27Relational Data at Box -Core Application Meta-Data
- 10:40Sharding Strategy
- 13:35Read-only Slaves
- 14:54Challenges
- 17:54Credence Architecture
- 18:34Incremental Development and Deployment
- 20:59Closing thoughts...
related talks
52mTo Shard or Not to Shard
49mSharding: from scratch to Yandex Disk
01h 00mThe Evolution of Databases at Dropbox
32mData @Scale Seattle- Eric Hwang introduced by Ganapathy Krishnamoorthy
46mDatabase Sharding the Right Way Easy, Reliable, and Open source
29mBuilding on Strengths, Learning from Differences
27mAutomatically shard & scale-out traditional databases on K8s
30mDatastore Axes: Choosing the Scalability Direction You Need
