3 ms·

> I think to manage private servers of that size you would need at least two extra experts totalling at least $20k/month. What? You set up the deployment once,

> I think to manage private servers of that size you would need at least two extra experts totalling at least $20k/month. What? You set up the deployment once, and then you only need to touch it when things go horribly wrong, which is every couple of months, or to make minor quick tweaks and run some updates. Let's be generous, and say you need 10 h/month, which is about 1/16 of a person-month. And if things go horribly wrong, everybody drops what they are doing to fix things, anyway, no matter if you're on AWS, dedicated/colo or run your own data center. When you significantly change your architecture/deployment, then you need to put in more time again, but if you build your code with need to scale and such things in mind from the get-go, then that won't come up much or at all.

PragmaticPulp 5y ago
> What? You set up the deployment once, and then you only need to touch it when things go horribly wrong, which is every couple of months Right, which is exactly why people pay extra for cloud managed services. If things are going “horribly wrong” every couple of months then you must necessarily be on call 24/7 and never take vacation or time away. In practice, you need at least two people to manage on-call coverage so you’re not completely uncovered if someone gets sick, decides to take vacation, wants to travel away from a computer and so on.
- southerntofu 5y ago
  We're talking volunteer-run projects, though. Who cares if it's not available 24/7? Best-effort is good enough. Those managed cloud services also fail often, you just have no information and no recourse about it.
- rndgermandude 5y ago
  Things go horribly wrong with AWS hosted stuff as well. And a lot of companies have a single-point-of-failure AWS person. While you're not wrong in general, nothing you just wrote is specific to running on dedicated servers vs AWS.
- lupire 5y ago
  Things go horribly wrong every year or so. The site goes down. It's fine. This isn't Facebook.

PragmaticPulp 5y ago

> What? You set up the deployment once, and then you only need to touch it when things go horribly wrong, which is every couple of months Right, which is exactly why people pay extra for cloud managed services. If things are going “horribly wrong” every couple of months then you must necessarily be on call 24/7 and never take vacation or time away. In practice, you need at least two people to manage on-call coverage so you’re not completely uncovered if someone gets sick, decides to take vacation, wants to travel away from a computer and so on.

southerntofu 5y ago
We're talking volunteer-run projects, though. Who cares if it's not available 24/7? Best-effort is good enough. Those managed cloud services also fail often, you just have no information and no recourse about it.
rndgermandude 5y ago
Things go horribly wrong with AWS hosted stuff as well. And a lot of companies have a single-point-of-failure AWS person. While you're not wrong in general, nothing you just wrote is specific to running on dedicated servers vs AWS.
lupire 5y ago
Things go horribly wrong every year or so. The site goes down. It's fine. This isn't Facebook.