The document discusses continuous deployment at the company kaChing. It advocates for deploying code changes continuously through automated processes as the safest approach. This allows building systems designed to fail and recover automatically through techniques like deploying to canaries, self testing, auto rollback, and exponential deploys. Continuous deployment is likened to an immune system with constant small failures and recoveries.

1. Continuous Deployment
at kaChing
Adam Rosien
Chief EffYoo Officer*, kaChing
adamr@kaching.com
@arosien
* false

2. True Story

3. $11
x1
0 12
“connect investors with
outstanding investment
managers”

4. ¬isCoder useless

5. undeployed code ==
warehouse space
$$

6. Deploying all the time is
the only way to be safe.

7. Building systems
designed for failures
is safer and faster than
trying to be perfect.

8. Continuous Deployment
Immune
System
Culture
Test Driven Continuous
Development Integration

9. “Continuous deployment
ends up looking to
services like tiny failures
and recoveries happening
all the time.”
@dfortunato

12. deploy canaries
self test

13. auto rollback
exponential deploys

14. commit messages
deploy services:
ONG-1212 Fixed NPE.
#release:um

15. zookeeper json collectd
nagios hudson ant rpm
yum jcollectd rrdtool
type-systems jmx
rabbitmq esper

16. zookeeper json collectd
nagios hudson ant rpm
yum jcollectd rrdtool
type-systems jmx
rabbitmq esper

17. zookeeper json collectd
nagios hudson ant rpm
yum jcollectd rrdtool
type-systems jmx
rabbitmq esper

19. Deploying all the time is
the only way to be safe.
Ship It!

20. youCanCode &&
hateAllTheCrapYouAre
ForcedToDealWith
? jobs@kaching.com
: devnull@kaching.com