container day - seattle

20
Why Docker? Boyd E. Hemphill @behemphi

Upload: boyd-hemphill

Post on 11-Apr-2017

575 views

Category:

Technology


0 download

TRANSCRIPT

Page 1: Container Day - Seattle

Why Docker?Boyd E. Hemphill

@behemphi

Page 2: Container Day - Seattle

@behemphi

What is The Goal of Your Company?

Page 3: Container Day - Seattle

The Goal

Make Money

@behemphi

Page 4: Container Day - Seattle

@behemphi

Containers are Hard

Page 5: Container Day - Seattle

Containers are Hard

BSD Jails (2000)

Solaris Zones (2004)

OpenVZ (2005)

LXC (2008)

@behemphi

Page 6: Container Day - Seattle

Containers are Hard

BSD Jails (2000)

Solaris Zones (2004)

OpenVZ (2005)

LXC (2008)

SILENCE

Docker (2013)

@behemphi

Page 7: Container Day - Seattle

@behemphi

Microservice = Micro Teams

Page 8: Container Day - Seattle

Microservices = Micro Teams

“Code to Interface” moves to infrastructure

Micro team’s service moves at its own pace

Coordination between people eased (Mythical Man Month)

Feature velocity increases

@behemphi

Page 9: Container Day - Seattle

Microservices = Micro Teams

“Code to Interface” moves to infrastructure

Micro team’s service moves at its own pace

Coordination between people eased (Mythical Man Month)

Feature velocity increases

@behemphi

Page 10: Container Day - Seattle

@behemphi

Build & Test Grids

Page 11: Container Day - Seattle

Build & Test Grids

Containers start in less than one second - faster builds

Can test more permutations of the system

Increase build parallelism

Increases feature velocity and innovation

@behemphi

Page 12: Container Day - Seattle

@behemphi

Configuration Mgmt

Page 13: Container Day - Seattle

Config Mgmt

Learning curve of typical CM tool is extremely steep

Docker obviates need for most host config (bakery)

Containers are configured via a simple bash-like file.

@behemphi

Page 14: Container Day - Seattle

@behemphi

Process Density

Page 15: Container Day - Seattle

Process Density

Reduce host consumption reduces cost

Reduces power footprint in large physical setting

@behemphi

Page 16: Container Day - Seattle

@behemphi

Dev Environments

Page 17: Container Day - Seattle

Dev Environments

New team members are productive their first day

Innovation - try new things quickly

Developers share improvements easily via familiar tools

@behemphi

Page 18: Container Day - Seattle

@behemphi

Black Box FTW

Page 19: Container Day - Seattle

Microservices = Micro Teams

Compliance over Governance

Ops role evolving to - Compliance as code.

@behemphi

Page 20: Container Day - Seattle

So thaaat’s why Docker?

Thanks @StackEngine!