How to organize the server part of the store for 1 million products?

Question

PHP

In general, there is a store, located on 1 VDS, already more than 300 thousand goods. We want to grow. How best to organize the server part. It is clear that we can no longer fit on 1 server, and I would like to spread the database into several servers in order to speed up processing. In which direction to dig, where can there be guides?

Answer 1

It's unclear. Who said you can't fit?
You start with monitoring and statistics, and then draw conclusions on the situation.
And then with a finger to the sky It is clear that we will no longer fit on 1 server ...

Answer 2

Look, this is not something to discuss on a toaster.
First, you need a developer who knows how to fault-tolerance. Then, based on his skills, you can talk with top admins who will be able to implement a fault-tolerant infrastructure for code.
Just like that, to take and spread the CMS on a bunch of servers is quite rare (and quite expensive).
And I'm not talking about the fact that "300k goods" is not at all a characteristic for planning the infrastructure of a project.

Answer 3

Add x2 RAM and that's it. The rest seems to be done more or less normally.

Answer 4

Look towards ArangoDB. At least zatyk on a DB clean.

Answer 5

It all depends on how actively users work with the item and what characteristics need to be processed. 1 million SKUs is common for any modern database. For 99%, information on the nomenclature is a rarely changed part that can be cached, the rest (availability and prices) does not require a lot of resources for 1 million records.