Service organization (2 servers, database transfer)?

Question

Database

Good afternoon. I am planning to develop a web service. The bottom line is that the service takes information from the api of one system, then processes the information and puts the data into the database.
I plan to use the following tools:
- php
- mysql
At first I thought to do everything on one server, but then I came to the conclusion that it would process a lot of information and the server could go down, so I think to split the service into two servers (one for receiving data and calculations, the other for work with service users):
1st step - takes information from api and puts it in an intermediate table
2nd step - process data from an intermediate table, and put it into a pre-implementation database.
Step 3 - we transfer the pre-realization database from the first server (calculated) and replace it with a database on server two (which is used by service users).
I have an assumption that the service base can grow very much and this will become a problem when transferring from one server to another - I really wanted to hear your opinion on this matter.
In general, I am glad for any advice and criticism on my scheme of the service. Thank you for your attention.

Answer 1

MySQL has server replication. The first master server contains tables step1, step2, step3. Set up replication on a ready-made table (step 3), and on the second mysql server you will have only processed data. Then you can remove the first base. and on the first disable replication