4 ms·
They kind of need to be there anyway, physically maintaining servers turns out to be a miniscule part of the whole maintenance. If you really care about uptime
by NohatCoder 3y ago
They kind of need to be there anyway, physically maintaining servers turns out to be a miniscule part of the whole maintenance. If you really care about uptime you still need people on-call who can intervene as necessary.
- gtirloni 3y agoIt's not a minuscule part of a small company. I made the point that on-premises makes sense after a certain scale. Once you have on-premises you need people that know switches, routers, rackmount server, hardware, virtualization, etc, plus keeping all of that properly maintained (security patches, IaC, periodic updates, analyzing performance, making sure it's properly architected, etc). I often see people saying it's the same cost or less but it's really not. Unless you have no idea what you should be doing.
- Scarblac 3y agoI don't know, I worked at a few companies that did this early in my career (early 2000s), and it was just the devs or the sysadmin of the office IT that did this sort of thing. There are lots of people who know enough about switches and routers to get them up and running. Virtualization, IaC, analyzing performance, right architecture etc is all for later, when you've grown enough to need that.
- gtirloni 3y ago> Virtualization, IaC, analyzing performance, right architecture etc is all for later, when you've grown enough to need that. Yeah, I think it might be a different perspective about when that all should be done. I tend to do that right from the beginning because I often see it snowball later on and nobody ever fixes it or does it "properly" (in my opinion, possibly not the right one). But that's a good point, no doubt.