How to choose the right server at the start of a project?

Question

MySQL

Hello, I have a question.
Now I'm opening my project, I'm thinking about buying a server.
Project on php (laravel) + mysql, redis The
question is, I want to take a dedicated machine, but I think with what characteristics is it better? Namely, I think by the amount of RAM and SSD.
Previously, the system administrator dealt with such issues, but I would like to understand this issue myself.
Actually, what exactly worries me: I would like to hear how you determine which server is needed at the start, willingly take it with a margin for future growth, and is it worth moving redis, mysql to a separate server (s) in advance? (i.e. buy >=2 servers).

Answer 1

1) Start with 4 gigs of RAM, use GVA, you can increase GVA at any time up, you can’t go down.
2) Don't take it out yet.
try
vdsina.ru/pricing
they are now optimal at a price in rubles.

Answer 2

You didn’t write anything about the expected load on the server, the amount of data and how this data will be processed (read / write ratio), whether there will be statics and how it will be processed - in general, nothing from which you can start when choosing a site. Draw at least an approximate architecture of the project so that they can help you.
If you don’t feel like it, take a cloud service (the same Forge, if you write in laravel), watch the load, starting from small. Some time of the resource's work will give you an understanding of where to dig further and how much money you will need in order to ensure the operation of the resource...

Answer 3

At random, for starters, you can generally collect and test on a virtual machine.

Answer 4

Everything is very simple - at the start, take measures so as not to be blocked by a specific host. Set up Ansible / Chef / Puppet so that at any time in 5 minutes you can raise the entire infrastructure anywhere. Conduct "exercises" in Vagrant and take the cheapest virtual machine.
Personally, changing a hoster takes me 30 seconds of my time - adding a new server to Jenkins and running 3 "Jobs": removing a backup, setting the environment and restoring the backup. I am sure that everything will be fine, because I periodically check the system.

Answer 5

It depends on the project itself.
For social networks with over 1000+ users need powerful hardware, less for a small project, etc.
The more specifics, the more opportunity to get a good answer)

Answer 6

The answer will not be until it is clear what kind of load. Your own server is an expensive toy (learn that you will have to pay for a unit in the provider's rack, ports, IP-s, power. All these are "fixed costs" that a startup should always minimize. When the project is in the black in terms of "variable costs", then you can already see how getting rid of some of them, and shifting to "fixed costs" to save.So sit down on virtual machines or a combination of Amazon services and go.