3 ms·
> How is it less complex to host your own... It is not less complex. It is definitely more complex and is harder. My point was that financially it is more sust
by pdimitar 8y ago
> How is it less complex to host your own...
It is not less complex. It is definitely more complex and is harder. My point was that financially it is more sustainable long-term. And once your org is bigger, dedicated Ops team gives much more peace of mind. Whoever is on shift flips 3 switches and things are back to normal in 2 minutes, 99% of the time. That is not always the case even with a huge provider like Amazon and Google.
> But the money the company I work for saves by not having to hire dedicated people to manage and babysit servers more than makes up for the cost of AWS.
Disagreed. Periodically, there pop up articles here in HN that prove with numbers and historical timelines that AWS only saves you time and white hair while you are smaller. Once you start to scale up and/or use more of their services, bills start to pile up quicker than before (people have mostly analyzed the exponential growth of their billing). Apologies that I don't keep the links but I remember that I've read at least 5 such articles in the last year, right here in HN.
> It just so happens that I know AWS well enough and have experience as an “architect” (and have the certifications to give them a warm and fuzzy) to be competent at the netops and devops side of things.
Good for you, many of us don't however. I honestly have no intention to either. It's a very specific vendor cloud system with a huge amount of proprietary tech baked in, and I have no desire to entangle my career prospects with its success. Career preferences. ;)
- scarface74 8y agoIt is not less complex. It is definitely more complex and is harder. My point was that financially it is more sustainable long-term. Can you set up a duplicate infrastructure that’s close to your international facilities worldwide cheaper? Even support would be cheaper because you can have one central team manage your worldwide infrastructure. Netflix moved their entire infrastructure to AWS. You’re not taking into account the cost of enploying people to babysit and do the “undifferentiated heavy lifting”, the cost of over provisioning just in case, the cost of the red tape to provision backup hardware for failover, etc. * And once your org is bigger, dedicated Ops team gives much more peace of mind.* You can easily outsource netops to a dozen companies that can be cheaper because they can manage multiple accounts and they can outsource the grunt work to cheaper labor. I know, I’ve worked in two companies that outsource day today management of netops. Whoever is on shift flips 3 switches and things are back to normal in 2 minutes, 99% of the time. That is not always the case even with a huge provider like Amazon and Google. You’ve never had to deal with a colo center. Have you ever dealt with AWS support as a representative of a large company? Disagreed. Periodically, there pop up articles here in HN that prove with numbers and historical timelines that AWS only saves you time and white hair while you are smaller. Once you start to scale up and/or use more of their services, bills start to pile up quicker than before (people have mostly analyzed the exponential growth of their billing). If the fixed cost of your infrastructure is growing faster than your revenue...you’re doing it wrong. Even if you can get simple VPS elsewhere (and yes you can). Thsts not where you get the win from AWS. You can host VPS anywhere and still take advantage of all of AWSs services. Good for you, many of us don't however. I honestly have no intention to either. It's a very specific vendor cloud system with a huge amount of proprietary tech baked in, and I have no desire to entangle my career prospects with its success. Career preferences. ;) That’s just what the original article said. You always tie yourself to a specific technology and risk that technology becoming out of favor. The trick is to stay nimble and to keep learning. Right now, there is a lot more money and opportunity in being a “Cloud Architect” than knowing how to set the same things up on prem.