Changes

Jump to: navigation, search

Identity/AttachedServices/StorageServiceArchitecture

89 bytes added, 04:39, 30 April 2013
Summary
* All reads and writes for a shard go to a single '''master''' MySQL database.
** This saves us having to deal with conflicting writes and othe multi-master headaches.
** To keep things simple, there are no read slaves. The sharding is the only thing responsible for distributing server load.
** A single DB host machine might hold multiple shards.
** To keep things simple, there are no read slaves. The sharding is the only thing responsible for distributing server load.
* Each master synchronously replicates to a '''hot standby''' in the same DC, to guard against individual machine failure.
Confirm
358
edits

Navigation menu