High Performance Ops for Enterprise PaaS

Dan Young | EngineerBetter | @dan0young

Adventures with small batch sizes in a big bank

The context

Global Bank

Thousands of Devs

Lots of Cloud Foundry

Traditional Ops

Image credit: thethreesisters

The beginning

Change is costly

Manual ops heroics

2-3 week release cycle

Big batches & high risk

Lots of rework

Our hopes

Influence attitudes to change

Faster cycle time

Happier, scalable team

Lower risk

Key technical ingredients

Cloud Foundry (commercial distro)

BOSH

Concourse CI

A well known public cloud

Results so far

Continuous Delivery

100% Reproducibility

Platform upgrades itself

First apps approved

Operations = Development

Cloud Foundry is itself Apps

Pairing, TDD, CI

Platform as a Product

Infrastructure as is Code

Communicate all the things

What have we learnt so far?

Kill dev/stage/prod naming

Build times are the enemy

‘Non-blocking pairs’ pattern

Self-reliance changes org dynamics

Co-located team

Small batch comms

Peer pressure is magic

Leaders create more leaders

Change radiating through people

Your story is yours alone.

Agile solves reveals problems

No secret recipes

No maturity models

Just continuous learning

http://yipa.org/training/online/on-demand/telling-your-impact-story/

@dan0young

dan.young@engineerbetter.com