Itai HochmanVP Engineering

Continuous Deploymentat Outbrain

Work procedures and culture that allow releasing code to production in very short cycles, multiple times a day

Continuous Deployment

Small Changes to Reduce Risks

Continuous Deployment

Continuous Deployment No Inefficient Waits (QA,

other features) Immediate feedback Loop Responsiveness Less Risk Fun, Fun, Fun

Continuous Deployment

Culture Architecture Tools

Continuous Deployment

Developers own their tasks Functional teams Architects embedded in the

Teams

Continuous Deployment

Continuously Prioritized Tasks Queues

Minimize Work In Progress (WIP)

Continuous Deployment

Definition of Done:Feature was releasedMonitoring shows Value

Continuous Deployment

Focus on ProductionEnvironment

Continuous Deployment

No Code branchesFrequent commitsUnit testing coverageFast Stable TrunkFeature flags

Continuous Deployment

Learning: Take ins Build, Measure, Learn

Continuous Deployment Immune system Unit tests Integration and Regression Self tests Monitoring system Alerts

Continuous Deployment

Co-Operation: Dev-ops Between the teams

Continuous Deployment

Architecture: Stand Alone Deployable

Services Build to Tolerate Failures Deploy frequently

Continuous Deployment Fun numbers: 5-50 production changes

every day More than 8000 APTs every

hour More than 6000 unit tests in

less than 10 minutes

Continuous Deployment Fun numbers: More than 50 different

services Takes less than 15 minutes

to deploy a service Services deployed if older

than 18 days

itai@outbrain.com

Thank YouItai Hochman