3 ms·

This is accurate in my experience. Also keeping things up and being there in case shit hits the fan is a full-time job. You can't write features and also manage

This is accurate in my experience. Also keeping things up and being there in case shit hits the fan is a full-time job. You can't write features and also manage servers equally well. Unless you have no life I guess.

wpietri 7y ago
Totally. I've had personal colo'd servers for 20 years at this point. But I'm tired of knowing that at any point I might have to wake up and haul my ass down to San Jose to swear at some piece of failing gear. I'm excitedly moving it all into the cloud.
- mcny 7y ago
  How far are you from you collocation? Is moving that closer an option?
  - wpietri 7y ago
    Colocation in SF proper is very spendy, which is how we ended up in San Jose. But waking up to go anywhere at 3 am to swear at gear is no longer on my list of fun activities. And there's no colo that will move the gear along with me when I go on vacation.
    - speleding 7y ago
      > there's no colo that will move the gear along with me when I go on vacation This is actually the main one for me. I've managed our own servers for a decade with almost zero downtime, and very little time spent at the colo. But you cannot safely go out of town without having someone else around who is familiar enough with your setup to deal with an outage. So moving stuff to AWS now almost entirely for that reason.
- krab 7y ago
  There is a middle ground. There are smaller companies where you can rent a bare metal server, usually with unmetered connection (priced by bandwidth). There is an on-call support 24x7 to replace any failing part when you call them. They can build custom servers and also give long term or bulk discounts. I have a good experience with [1] (a smaller local company) and Hetzner [2], a bigger provider. Compare the prices with cloud. Especially if you need something RAM intensive. [1]: https://www.superhosting.net/dedicated-servers https://www.superhosting.net/dedicated-servers [2]: https://www.hetzner.com/dedicated-rootserver https://www.hetzner.com/dedicated-rootserver

wpietri 7y ago

Totally. I've had personal colo'd servers for 20 years at this point. But I'm tired of knowing that at any point I might have to wake up and haul my ass down to San Jose to swear at some piece of failing gear. I'm excitedly moving it all into the cloud.

mcny 7y ago
How far are you from you collocation? Is moving that closer an option?
- wpietri 7y ago
  Colocation in SF proper is very spendy, which is how we ended up in San Jose. But waking up to go anywhere at 3 am to swear at gear is no longer on my list of fun activities. And there's no colo that will move the gear along with me when I go on vacation.
  - speleding 7y ago
    > there's no colo that will move the gear along with me when I go on vacation This is actually the main one for me. I've managed our own servers for a decade with almost zero downtime, and very little time spent at the colo. But you cannot safely go out of town without having someone else around who is familiar enough with your setup to deal with an outage. So moving stuff to AWS now almost entirely for that reason.
krab 7y ago
There is a middle ground. There are smaller companies where you can rent a bare metal server, usually with unmetered connection (priced by bandwidth). There is an on-call support 24x7 to replace any failing part when you call them. They can build custom servers and also give long term or bulk discounts. I have a good experience with [1] (a smaller local company) and Hetzner [2], a bigger provider. Compare the prices with cloud. Especially if you need something RAM intensive. [1]: https://www.superhosting.net/dedicated-servers https://www.superhosting.net/dedicated-servers [2]: https://www.hetzner.com/dedicated-rootserver https://www.hetzner.com/dedicated-rootserver