D3Sharding

The problem

1 s on screen = 100 ms

Copies help with reads. What do you do when the writes alone are too many?

Every write lands on one database

45 requests a second, mostly writes, on one database that can do about 33.

Live metrics for each version of the scene
Metric	One database	Shards	Change
target ≤ 400 ms	—	—	—
	0%	—	—
	—	—	—
	—	0%	—

D3Sharding

When writes outgrow one machine, split the data by key so that each database owns only a slice of it.