Asklemmy

43896 readers

964 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
[email protected]: a community for finding communities

~Icon~ ~by~ ~@Double_[email protected]~

founded 5 years ago

MODERATORS

[email protected]

How to scale MySQL horizontally? (programming.dev)

submitted 10 months ago by [email protected] to c/[email protected]

12 comments fedilink hide all child comments

What is the industry/production grade solutions or if you have already any experience please share it. Thanks

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

[–] [email protected] 6 points 10 months ago (1 children)

Use postgres

[–] [email protected] 3 points 10 months ago* (last edited 10 months ago) (1 children)

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.