2 ms·
First, "the DevOps profession" is one of two major uses of the term "DevOps," and, in my opinion, an erroneous one. But words are defined by how they're used, s
by geofft 10y ago
First, "the DevOps profession" is one of two major uses of the term "DevOps," and, in my opinion, an erroneous one. But words are defined by how they're used, so we have to deal with this.
You can see "DevOps" as a mindset, that developers should understand how to operationalize their code and ops staff should understand how to write and debug the code they're maintaining. That is the original idea: there used to be a lot of resistance to the idea that devs should care about deployment or that ops folks should be expected to program.
You can also see "DevOps" as a role, meaning sysadmins who know how to code. That's largely becoming less of a role, I hope, due to some combination of all sysadmins being expected to code (except in non-best-practices environments like large banks or small startups with opinionated people), and "DevOps" in the previous sense becoming more successful. AWS is certainly part of it, because it makes it more possible for someone with a developer skillset to deploy a working app, but devs have been pinch-hitting as ops for decades and it hasn't killed the ops profession.
That said, knowing software engineering doesn't imply a knowledge of AWS, and it certainly doesn't imply a knowledge of how to evaluate tradeoffs in AWS - should you make the code more complex to span AZs? Should you deploy cool software on EC2 boxes or use AWS's managed infrastructure? Should you store certain data in S3 or in a normal filesystem? If it's in S3, should you make it directly accessible or proxy it through your app? etc. That will continue to be a skillset, and there will always be times when "install normal software in EC2" will be the right answer and therefore necessitate the entire old-school ops skillset. And for many industries, there will also be times when "actually, don't put this in the cloud" is the right answer, too. So from that perspective, I would certainly not say that AWS is killing the ops profession, whether you call it "ops" or "DevOps". Of course your ability to properly terminate a SCSI bus is no longer of much value, but that's true whether or not AWS is around.