4 ms·
This is SO myopic. You think bad things don't happen on AWS? You think that an experienced admin isn't going to spend significantly more time trying to communi
by johnklos 6y ago
This is SO myopic.
You think bad things don't happen on AWS? You think that an experienced admin isn't going to spend significantly more time trying to communicate with an actual human at Amazon than fixing a problem on a physically controlled server?
This is incredibly naive.
- EdwardDiego 6y agoWe moved to AWS because bad things happen there less often than they were happening to us with various DC providers we used to use. I've never had AWS tell us that they can't find the server we're renting that suffered HDD failure. AWS has never cut us off from the Internet because a sysop typed a command in the wrong session. And we find AWS support to be far quicker to respond, and far more effective, than our previous providers. So, YMMV, but AWS is pretty damn good for our requirements.
- therealx 6y agoI agree with you, but I can't find a good way to communicate this to the other camp. I wonder if you can't clearly see this without having been a "sysadmin" long before "devops" was a title.
- ldng 6y agoIt's just that they have a vested interest in not understanding or even acknowledge your arguments. Scalability is the thing and AWS its Viagra. Whoever has the biggest scalability get to pat itself in the back.
- pensatoio 6y agoIt's both myopic and naive to assume there's a binary set of circumstances that lend an upper hand to self-hosting or cloud hosting. It's a sliding scale. What makes you money? What's your expected growth? What are your security needs? What experience does your team have? In this thread, people at each end of the scale are 1. conflating different use cases (wordpress is not the same as a massive, scaled data ingest pipeline) and 2. are ignoring the hidden costs of both.