Timeline for Managing 100s of similar databases
Current License: CC BY-SA 4.0
10 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Feb 12, 2019 at 5:05 | history | edited | Slawomir | CC BY-SA 4.0 |
deleted 85 characters in body
|
| Feb 12, 2019 at 4:38 | comment | added | Slawomir | The distribution of accounts to instances can be by hash, customer "size" or load. The nice thing about schema-per-account is that reallocation is possible. So a few busy customers can be assigned to an instance with much fewer co-located customers. | |
| Feb 12, 2019 at 4:35 | comment | added | Rick James | Don't be rigid about 100 per shard. You might get some very busy customers on one shard while having idle or defunct customers on another. | |
| Feb 12, 2019 at 4:34 | history | edited | Slawomir |
edited tags
|
|
| Feb 12, 2019 at 4:33 | comment | added | Rick James | You have tagged it with "NDB Cluster". Perhaps you meant "sharding"? | |
| Feb 11, 2019 at 22:15 | comment | added | Slawomir | The reason isn't just "good" - I could fight that one - it's mandated by the regulations. | |
| Feb 11, 2019 at 22:07 | history | edited | Slawomir | CC BY-SA 4.0 |
added 1973 characters in body
|
| Feb 11, 2019 at 21:38 | comment | added | Mr Zach | Might be a good reason for this databse design, but if its not, maybe you should look into transforing this into a "one databse, multiple customers" solution. | |
| Feb 11, 2019 at 21:19 | answer | added | RolandoMySQLDBA | timeline score: 1 | |
| Feb 11, 2019 at 20:52 | history | asked | Slawomir | CC BY-SA 4.0 |