Flickr (2009)

• 10+ Deploys per day
• Traditional thinking about Dev and Ops
• Business requires change
• Change risk management

http://es.slideshare.net/jallspaw/10-deploys-per-day-dev-and-ops-cooperation-at-flickr

Flickr (2009)

1. Automated infrastructure
2. Shared cersion control
3. One step build and deploy
4. Feature flags
5. Shared metrics
6. IRC/IM robots

http://es.slideshare.net/jallspaw/10-deploys-per-day-dev-and-ops-cooperation-at-flickr

Flickr (2009)

• Respect
• Communication
• Trust
• Attitude on failure
• Avoid blame

http://es.slideshare.net/jallspaw/10-deploys-per-day-dev-and-ops-cooperation-at-flickr

LinkedIn (2011)

• Release rate overflowed deploy rate
• Gap reducing because of tooling (ZenOSS, Splunk, ...)
• Horizontal relationships added to vertical ones

http://dev2ops.org/2011/07/devops-days-mountain-view-2011-linkedins-devops-journey-video/

LinkedIn (2011)

• Following DevOps
  • Self provisioning capabilities
  • Continuous CM and code deploy
• Ops enables and supports organization
• Focus
  • Critical hardware management
  • Horizontal software infrastructures

http://dev2ops.org/2011/07/devops-days-mountain-view-2011-linkedins-devops-journey-video/