Stategies for scaling out MySQL/MariaDB when database gets too large for a single host? (programming.dev)

submitted 1 month ago* (last edited 1 month ago) by [email protected] to c/[email protected]

3 comments fedilink hide all child comments

What are your preferred strategies when a MySQL/MariaDB database server grows to have too much traffic for a single host to handle, i.e. scaling CPU/RAM or using regular replication is not an option anymore? Do you deploy ProxySQL to start splitting the traffic according to some rule to two different hosts?

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?

top 3 comments

sorted by: hot top new old

[-] [email protected] 5 points 1 month ago

Have you actually analyzed what your real bottleneck is?

[-] [email protected] 2 points 1 month ago

I am asking for general strategies, not for a solution to a specific case.

[-] [email protected] 2 points 1 month ago

Well general strategies are going to depend on where the bottleneck is, so the main general strategy is simply to find the bottleneck. From there, there may be other general strategies one would use for those, but there's so many possible starting places, it's hard to give any specifics as they all depend on what the bottleneck actually is.

this post was submitted on 06 May 2025

9 points (100.0% liked)

DevOps

1856 readers

2 users here now

DevOps integrates and automates the work of software development (Dev) and IT operations (Ops) as a means for improving and shortening the systems development life cycle.

Rules:

Posts must be relevant to DevOps
No NSFW content
No hate speech, bigotry, etc
Try to keep discussions on topic
No spam of tools/companies/advertisements
It’s OK to post your own stuff part of the time, but the primary use of the community should not be promotional content.

Icon base by Lorc under CC BY 3.0 with modifications to add a gradient

founded 2 years ago

MODERATORS

[email protected]