4 ms·

Devs are those who dabble in code. Ops are those who run and administer systems that run the code. Devops is the act of codifying your operations. Automating d

Devs are those who dabble in code. Ops are those who run and administer systems that run the code. Devops is the act of codifying your operations. Automating deployments, ci/CD things like that. Putting alert and monitoring systems in place. That's my understanding.

nodesocket 7y ago
The following bullet points encapsulate DevOps to me: - Codifying infrastructure with tools such as Packer, Terraform, Ansible. The infrastructure should be just as auditable, repeatable, and transparent as the code. - Empowering and allowing the engineers who write code to deploy it. - Immutable servers/containers. - A solid suite of monitoring and alerting tools that auto-heal (preferred) or at least notify when things go wrong.
- ryeguy_24 7y ago
  I think 1 and 3 are just certain ways of doing DevOps. Out of the 4, I think 2 seems most accurate.
  - paulddraper 7y ago
    #2 is the human combination of Dev and Ops #1 is the technological combination of Dev and Ops #3 is a corollary to #2 #4 is just good Ops
jiveturkey 7y ago
That's not it. Those are all things your normal (non-devops) ops teams do. Ops teams run the gamut from "I can barely install an rpm, we have dedicated people to configure postfix", to teams that write their own batch scheduling systems. At the high end, we call these teams SREs. At the low end, tier-1 helpdesk. Devops is when those things cross over into normal developer work. The developers take on these "ops" duties themselves. It may or may not involve actual development. It always involves devs having to understand the infrastructure their code runs on. Done right, it's a good thing. It makes devs sensitive to how their code is deployed and run in production, without being able to blame some other team for the application not performing well, not having adequate availability, etc. Usually, it's not done right.

nodesocket 7y ago

The following bullet points encapsulate DevOps to me: - Codifying infrastructure with tools such as Packer, Terraform, Ansible. The infrastructure should be just as auditable, repeatable, and transparent as the code. - Empowering and allowing the engineers who write code to deploy it. - Immutable servers/containers. - A solid suite of monitoring and alerting tools that auto-heal (preferred) or at least notify when things go wrong.

ryeguy_24 7y ago
I think 1 and 3 are just certain ways of doing DevOps. Out of the 4, I think 2 seems most accurate.
- paulddraper 7y ago
  #2 is the human combination of Dev and Ops #1 is the technological combination of Dev and Ops #3 is a corollary to #2 #4 is just good Ops

jiveturkey 7y ago

That's not it. Those are all things your normal (non-devops) ops teams do. Ops teams run the gamut from "I can barely install an rpm, we have dedicated people to configure postfix", to teams that write their own batch scheduling systems. At the high end, we call these teams SREs. At the low end, tier-1 helpdesk. Devops is when those things cross over into normal developer work. The developers take on these "ops" duties themselves. It may or may not involve actual development. It always involves devs having to understand the infrastructure their code runs on. Done right, it's a good thing. It makes devs sensitive to how their code is deployed and run in production, without being able to blame some other team for the application not performing well, not having adequate availability, etc. Usually, it's not done right.