Confirmed users
358
edits
Identity/AttachedServices/StorageServiceArchitecture/MySQLStorageCluster: Difference between revisions
Identity/AttachedServices/StorageServiceArchitecture/MySQLStorageCluster (view source)
Revision as of 05:27, 11 June 2013
, 11 June 2013no edit summary
(Created page with "== A Massively-Sharded MySQL Cluster == One of the leading options for storage is a massively-sharded MySQL setup, taking advantage of the highly shardable nature of the data...") |
No edit summary |
||
| Line 1: | Line 1: | ||
= | = MySQL Storage Cluster = | ||
One of the leading options for | One of the leading options for implementing the [[PiCL Storage Service|Identity/AttachedServices/StorageServiceArchitecture]] is is a massively-sharded MySQL setup, taking advantage of the highly shardable nature of the data set. Basic principles: | ||
* Each user is | * Each user is transparently mapped to a shard via e.g. consistent hashing | ||
* All reads and writes for a shard go to a single '''master''' MySQL database. | * All reads and writes for a shard go to a single '''master''' MySQL database. | ||