Database

159 readers

1 users here now

founded 5 years ago

MODERATORS

Trevis@lemmy.ml

What to do when a MySQL/MariaDB database gets too large for a single host? (programming.dev)

submitted 2 months ago by otto@programming.dev to c/database@lemmy.ml

3 comments fedilink hide all child comments

What are your strategies when a MySQL/MariaDB database server grows to have too much traffic for a single host to handle, i.e. scaling CPU/RAM is not an option anymore? Do you deploy ProxySQL to start splitting the traffic according to some rule to two different hosts? What would the rule be, and how would you split the data? Has anyone migrated to TiDB? In that case, what was the strategy to detect if the SQL your app uses is fully compatible with TiDB?

you are viewing a single comment's thread
view the rest of the comments

[–] lurch@sh.itjust.works 2 points 2 months ago

Usually, first replication, then ProxySQL. But often the devs can optimize the app that uses it in parallel, eg. with caching some things in RAM, on disk or in redis or not selecting * when they only need two fields of the table etc..