Should the DB be running on a separate machine?

Question

System administration

Now there is a site and a database that work in managed cloud hosting.
There was a need to transport this stuff to VPS.
All this will work in one copy, without dockers.
And the question arose - does it make sense to distribute the database and the site to different VPS, or can they work on one?
From the point of view of the "correctness" of the architecture, it seems that such a division makes sense - each server has its own resources and is guaranteed, and it will be easier to scale in the future.
On the other hand, it seems that there is some overengineering and a solution to a non-existent problem in this. Also, joint work will favorably affect the speed.
What problems can arise in both options, and which way is better to go? Or is there no difference?

Answer 1

Are there performance issues? If not, put on one machine. Well, if you are spreading, do not forget about one nuance, the machine with the database should have been nearby, otherwise network delays will kill the whole idea.