Is it worth splitting the database?

Question

MySQL

Let's say we have a MySQL (innoDB) database:
users
user_statuses
user_*
...
...
letters
letter_statuses
tasks
...
etc. Let's
assume that the database will grow at a huge pace, does it make sense to scatter entities across different databases? Let's make a separate database to store users, mailing lists, tasks, etc.? Will it help in the future?

Answer 1

if you can scatter your data like that, then you can then set up sharding when the place runs out. And you should resort to sharding when there is not enough memory (for example, I now have a nice little server with 256 gigs of RAM, there are cooler guys).

Answer 2

Timely sharding/replication will help.

Answer 3

If you have thousands of visitors per day, and if a million records are added to the database in a month, then it’s worth it, otherwise not!

Answer 4

Modern databases are originally designed to work with millions of records, they work with them quite well.
If you are planning to reach hundreds of millions of records, you can think about splitting right away.
Here it is better to spread the main (most loaded) table to different servers (for example, users from A to F on one server, users from Z to T on another server, users from Y to Z on the third server, if your main table is users, if you store all the inhabitants of Europe there.On
the other hand, there is a load on writing and reading.On
the third hand, if you make not only a database, but also servers that process data, it will still be
cooler.Doing it on one server makes no sense there is no, superfluous troubles.

Answer 5

That's when it starts to grow at a "huge" pace, then and only then will it make sense.
By the way, what are these "huge" ones?