28
How to scale MySQL horizontally?
(programming.dev)
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 03 Jan 2024
28 points (93.8% liked)
Asklemmy
43781 readers
887 users here now
A loosely moderated place to ask open-ended questions
Search asklemmy ๐
If your post meets the following criteria, it's welcome here!
- Open-ended question
- Not offensive: at this point, we do not have the bandwidth to moderate overtly political discussions. Assume best intent and be excellent to each other.
- Not regarding using or support for Lemmy: context, see the list of support communities and tools for finding communities below
- Not ad nauseam inducing: please make sure it is a question that would be new to most members
- An actual topic of discussion
Looking for support?
Looking for a community?
- Lemmyverse: community search
- sub.rehab: maps old subreddits to fediverse options, marks official as such
- !lemmy411@lemmy.ca: a community for finding communities
~Icon~ ~by~ ~@Double_A@discuss.tchncs.de~
founded 5 years ago
MODERATORS
I'm glad someone else said it... It may sound glib but the performance limits between Postgres and MySQL are night and day.
More seriously though... Read replication is how you horizontally scale any RDBMS. Read replication unlocks a serious amount of read bandwidth but it comes at a (usually steep) technical cost to migrate logic to be handle aware - especially when it comes to complex transactions.
I provided a "real" answer, but I think it's important to realize that MySQL is far behind the game in terms of performance... The Oracle acquisition really fucked that software and it hasn't recovered.
Anyways, horizontal scaling means replicas... But the specifics of that (and resources to aide with it) are highly dependent on their infrastructure... Self hosted? AWS RDS? Aurora? All those have really different starting points when considering a migration.