-
Notifications
You must be signed in to change notification settings - Fork 0
Principles
“Only a fool learns from his own mistakes. The wise man learns from the mistakes of others.” ― Otto von Bismarck
The principles listed below are inputs into our planning and decision making. We make an effort to promote our experience to our list of principles.
In 2012, Dr. Gene Kim distilled the essence of DevOps into three simple Principles. These principles are described in a 2012 article entitled, The Three Ways: The Principles Underpinning DevOps
- The First Way: Systems Thinking
- The Second Way: Amplify Feedback Loops
- The Third Way: Culture of Experimentation and Learning
The CWDS DevOps Engineering Team is constantly seeking ways to improve the flow of application components from concept to production deployment by reducing developer friction, identifying and correcting technical and process bottlenecks, and by creating an environment that is reliable and consistent for developers to create, build, and test software so they can fail fast. For more information about the Three Ways, we suggest that you consider reading The DevOps Handbook.
- Public Dollars Spent on Public Goods
- Infrastructure As Code
- HTTPS Only
- DRY - Don't Repeat Yourself
- Internal Cohesion, External Decoupling
- All application environments have the exact same structure
- Get to a known state, and stay there
- When given the choice of two equal value outcomes, choose the one that makes future change easier.
- Security at every decision point
- Immutable infrastructure
- Emergent Architecture/ Emergent Design
- Where they apply, we follow the 12 Factors defined by The Twelve-Factor App
Additional Principles of DevOps, as described by John O'Duinn
- Measure success in terms of souls saved, as well as the usual metrics
- Measure obsessively
- Build to scale
- Use multiple regions
- Trust that everything will fail eventually
- Make it visible; show progress
- Start small and build out
- Deliver the product and pipeline