Continuous Delivery! ! Isa Goksu! Head of Enterprise Architecture,! Istanbul Stock Exchange

Agenda • Level Set! • Very rough outline of IMKB delivery mechanism! • Who cares?! • What is Continuous Delivery! • What is Continuous Delivery Pipeline!

Level Set • Some terminology! • SDLC! • Waterfall vs Agile! • Continuous Build / Integration / Deployment / Delivery! • DevOps! • Infrastructure as code & Configuration Management! • Quality Assurance! • MTBF & MTRS

Software Development Life Cycle (won’t cover)

Waterfall (won’t cover) • Adapted from manufacturing! • Introduced by Winston Royce as a practice that should NOT BE followed in his book

Agile 101 (won’t cover) • Declared in Agile Manifesto around 2001! • 4 core ideas! • Individuals and interactions over processes and tools! • Working Software over comprehensive documentation! • Customer Collaboration over contract negotiation! • Responding to Change over following a plan! • 12 principles around working software! • Many implementations! • Scrum, Kanban, Lean, Scrum-ban, Crystal, etc..

Agile 101

Continuous What? • Continuous Build (won’t cover)! • An automated build from mainline! • Continuous Integration (won’t cover)! • An automated build from mainline! • An automated testing suite (unit, integration)! • Measuring quality of the code base! • Continuous Deployment (won’t cover)! • Continuously deploying into a prod-like environment! • An automated testing suite (acceptance)

DevOps (won’t cover) • Introduced by Patrick Debois! • Key principles! • Communication! • Collaboration! • Integration! • Everything should be automated, repeatable w/o risk Dev  +  QA  +  Ops

Infrastructure as Code (won’t cover) • Infrastructure should be treated as code! • Outcomes should be deterministic & predictable! • Modeling infrastructure rather than on-demand ops on it! • And many other core values! • Who uses?! • Amazon handles 2 major EC2 DC’s with this (close to 500K machines)! • Facebook manages 150K machines! • Google manages 40K machines

Quality Assurance (won’t cover) • Allows quality to be transparent! • 5 major test blocks! • Regression (automated)! • Smoke (automated)! • Acceptance (automated)! • Performance (periodical)! • Load (periodical)! • Exploratory Tests (every time)

MTBF & MTRS (won’t cover) • Mean Time Between Failures! • Mean Time Recovery of Service! • Business (therefore project) dependent! • Real-time systems usually goes for MTRS! • 0-ing MTBF removes the need for MTRS

Continuous Delivery! from where we left..

Rough Outline • Different cultures, techniques and methodologies! • No global visibility (monitoring, errors, reporting, etc)

Rough Outline • Different priorities! • No clear delivery path + out-of-date docs

Rough Outline • Indispensable people + overtime, overtime, overtime ! • Not sustainable (kills passion + quality)! • Keeping business promises?

Who cares?

Really?

Is there a Silver Bullet? • Not really! • Failure will always happen, and we should accept that!! • What do we do then?! • We should be ready for it!! ! ! Let’s look at some case studies..

Case Study: Netflix • Zero downtime! • 27.1M users with average 7GB/month! • Yeap, that is 189 EB average! • Killer bots

Case Study: Google Wallet • Zero downtime! • $8B annually! • 192M users! • Only <50 people built it

How did they do? • Small and frequent releases! • One pipeline! • Repeatable & risk-free deployments! • Always production ready philosophy! • DevOps

Case Study: Flickr • Small and frequent releases

Continuous Delivery • Philosophy! • Automation! • Patterns & Practices! • Collaboration! • Ingredients! • Configuration Management! • Continuous Integration! • Automated Testing

Continuous Delivery • Only valid measure of software: production readiness! • Super Fast feedback loop! • Business decides, IT follows

Continuous Delivery • Clear visibility with Continuous Delivery pipeline! • Quality has to be built into the product! • Priority is not on the features, it’s always on

Continuous Delivery Pipeline

Continuous Delivery Pipeline • Pipeline tries to prove your software is broken! • Creativity can only be done by fast feedback! • Fungible and cross functional teams! • Repeatable, risk-free, proven and visible by everyone! • Anybody can do it!