|
|
|
|
|
by theshrike79
1974 days ago
|
|
> Ultimately, you are probably stuck in the cloud until you can hit that point of being able to dedicate 2+ full-time engineers to the task of managing your infrastructure This is the exact reason people stay on AWS. You need to be big and decently profitable to afford 2+ full time people managing the server hardware purchases, maintenance, updates - same with network. These people need to be 24/7 on-call unless you can somehow make your system so fault-tolerant, that it can handle up to 16 hours of downtime without intervention (breaks the second the engineer clocks out, needs to hold its own until they clock back in). Even the two people are a stretch when you need to be 24/7, that's at least 3 shifts and even then you're one flu away from being short-staffed again. So now we're at a point where you need to make enough profit to pay 4 competent server engineer's salaries just to get out of AWS. Add to that the one-time costs of buying your own servers, setting them up and colocation costs. That's a lot. |
|