<story><title>Rolling your own servers with Kubernetes</title><url>https://gravitational.com/blog/aws_vs_colocation/</url></story><parent_chain></parent_chain><comment><author>ranrotx</author><text>AWS employee here--thoughts and opinions are my own.&lt;p&gt;Prior to AWS, I was in IT Operations at a large financial services company. I saw the writing on the wall that over time, companies would not want to manage this part of their IT  infrastructure themselves. Keep in mind, I was someone who was responsible for keeping the lights on for a decent number of Linux severs.&lt;p&gt;For an individual company, there really isn&amp;#x27;t much value in having to maintain firmware levels on all your hardware, patch hypervisors (and try to coordinate all of the maintenance around a fixed pool of hardware), perform months-long evaluation of new hardware before purchasing, test and validate configurations on new hardware, etc. I used to do all of this. I don&amp;#x27;t miss it either.&lt;p&gt;Yes, the items above are important, but doing them right is really table-stakes for any reliable IT Operations department. You can choose to spend time getting these right, or delegate that responsibility to a service provider whose main job is to get that stuff right (and recoups that cost across a much larger customer base).</text></comment>
<story><title>Rolling your own servers with Kubernetes</title><url>https://gravitational.com/blog/aws_vs_colocation/</url></story><parent_chain></parent_chain><comment><author>diehunde</author><text>So before we had an IT team that would maintain the bare metal servers. Now we need &amp;quot;Cloud Engineers&amp;quot; to maintain the cloud infrastructure working properly. I don&amp;#x27;t know if the argument of externalize the maintenance of the servers is valid since the complexity of the cloud services is just increasing everyday.</text></comment>