Sharding

Table of contents

• Overview
• Preparation of the shards (MariaDB database instances)
  • Create test data
  • Creating roles and users
  • MaxScale Monitor User
  • MaxScale Admin User
  • Create application role and accounts
  • Proxy protocol
• MaxScale SchemaRouter configuration
• Starting and stopping the MaxScale Load Balancer
• Application tests
  • Simple application tests
  • New command show shards
  • More general test
  • Less simple tests
  • More complex application tests
  • Cross-shard tests
• Operation of a MaxScale sharding system …

As already mentioned earlier, we roughly have a hand full of customers which are playing with the though of sharding solutions. They typically have many different customers (clients, tenants) and the number of customers becomes so huge (thousands to millions) that one machine cannot cope with the load any more.

So splitting the load by customers to different machines makes sense. This is quite easy when customers are separated per schema. In the good old times of Open Source our customers have implemented …

Once in a year or so we get a request of a customer about MariaDB/MySQL sharding solutions. So here we have a list of sharding solutions we are currently aware of:

• MySQL Fabric: A Brief Introduction to MySQL Fabric This product is discontinued by MySQL in the meanwhile!
• Spider Storage Engine for MariaDB: Spider Storage Engine Overview
• MariaDB MaxScale: Simple Sharding with Two Servers and Schema Router
• ProxySQL: Sharding in ProxySQL
• PingCap TiDB (Titan DB): Release Candidate der verteilten Datenbank TiDB …