Continuous Happiness by Continuous Delivery

continuous happiness

continuousdelivery

by

bebetterdeveloper.com@sergejusb

sergejus barinovas

100+releases / day at

8minto spin 500 cassandras at

fact

s

25+releases / day at

fact

s

WHYBU

T

rare releases

higher risk

frequent releases

lower risk

HOWBU

T

continuousdelivery

by

continuous delivery

RAPIDLY

REPEATEDL

Y

RELIABLY

push

tech

niq

ues

to

features

bug

fixes

low riskminimal

manualoverhead

out

AT

WIT

H

contin

uous d

eliv

erycontinuou

s integration

continuous deployment

infrastructure automation

continuous integration

con

tin

uou

s in

teg

rati

on

auto

mat

ed

test

s

automated

builds

versioncontrol

version control

always version your files

1

make it source of truth2

3 make it friendly to use

distributed over centralized

4

perfo

rce

SVNTF

S

GIT

mercurialbazaar

automated tests

design for testability1

make them part of DNA2

3 make them fast & reliable quality over quantity4

fake

s

stu

bs

mock

s

integrationfunctional

UNIT

automated builds

make them effortless1

always use CI servers2

3 make them discoverable

jenkinshudsonT

FSteamcity

contin

uous d

eliv

erycontinuou

s integration

continuous deployment

infrastructure automation

continuous deployment

con

tin

uou

s d

ep

loym

en

t

deploymentpackages

depl

oym

ent

dash

boar

d

monitoring

& metrics

deployment packages

scripts over manual work

1

externalize configuration

2

3 make them part of CI

MAKERAKE

power shellpython

deployment dashboard

use automated deploy tool

1

make it visual & easy2

3 trust over restrictions

keep everyone informed

4

G Ooctopus

capistrano

monitoring & metrics

for hardware & software

1

make it visual & easy2

3 make it reliable

use it for business4

muninnagios

zab

bix ganglia

cacti

contin

uous d

eliv

erycontinuou

s integration

continuous deployment

infrastructure automation

infrastructure automation

infr

ast

ruct

ure

au

tom

ati

on

singl

e se

rver ecosystem

single server

start with configuration1

externalize parameters2

3 run it constantly

make it visual & easy4

puppet chef

ecosystem

join with templates1

join with release packages

2

3 join with monitoring

make it for cluster4

contin

uous d

eliv

erycontinuou

s integration

continuous deployment

infrastructure automation

sergejus barinovas

thanks

bebetterdeveloper.com@sergejusb