Identity/AttachedServices/StorageServiceArchitecture/MySQLStorageCluster: Difference between revisions

(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...")
 
 
(2 intermediate revisions by the same user not shown)
Line 1: Line 1:
== A Massively-Sharded MySQL Cluster ==
= MySQL Storage Cluster =


One of the leading options for storage is a massively-sharded MySQL setup, taking advantage of the highly shardable nature of the data set.  Basic principles:
One of the leading options for implementing the [[Identity/AttachedServices/StorageServiceArchitecture|PiCL Storage Service]] is a massively-sharded MySQL setup, taking advantage of the highly shardable nature of the data set.  Basic principles:


* Each user is transaprently mapped to a shard via e.g. consistent hashing
* 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.
Confirmed users
358

edits