Skip to content

Instantly share code, notes, and snippets.

What would you like to do?
Devops Best Practices

DevOps started out as "Agile Systems Administration". In 2008, Andrew Shafer did a talk called "Agile Infrastucture" addressing issues around involving more of the company in the same disciplines as programmers.

In 2009, Patrick Debois created "DevOpsDays" conference to help to bring it to light. However, it wouldn't begin to trend until about 2010, when people would begin to describe it as a standalone discipline.

Today, DevOps goes beyond just developers, systems administration and infrastructure, its about dev, ops, agile, cloud, open source and business, everything.

DevOps is a movement. There's no certificate, role, set of tools or prescriptive process. There's no specification, it's not a product, or job title. There's no one true voice on what DevOps is or isn't. It's about attitude, ideas, customs and behaviours. Culture, paradigms and philosophy. It's a way of thinking, a way of doing and a way of being. Practicing as well as preaching. It's a conversation. It's about taking the best experiences and sharing those with others.

There are some very important qualities, principles and techniques that have proven to work, that everyone should be aware of, they are the best practices.

Let's explore those...

Though not necessarily accurate, I've broken them down into their evolutionary stages to make fit easier to digest...

Waterfall to Agile

Agile to Lean

Lean to Continuous Integration

Continuous Integration to Continuous Delivery

Continuous Delivery to Continuous Deployment

Continuous Deployment to Continuous Operations

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment