Humpty Dumpty: A Story of API DevOps Gone Wrong

Emily Dowdle
Wazee Digital

I’m convinced Humpty Dumpty is a story of DevOps gone wrong.

Humpty Dumpty sat on a wall,
Humpty Dumpty had a great fall.
All the king’s horses and all the king’s men
Couldn’t put Humpty together again.

First, who asks a horse to do surgery? Hoofs can’t hold scalpels. Second, either the king’s men are inept or they’re not communicating. Two kindergarteners with some Elmer’s could have done the job.

You see, Humpty is a deploy. He was fine in staging but shit the bed in production. Now the site’s down and your boss is threatening everyone’s jobs. IT is saying the code is broken. The developers are saying it’s a server issue.

Meanwhile, Humpty is bleeding out. And your customers are complaining on Twitter. Which means a customer service rep has entered the #incident channel to tell you the site’s down. Yea, no shit, Tom.

Sound familiar?

DevOps is the new Agile. Everyone “does it” but few fully embrace it.

This talk will focus on common pitfalls and how to ensure your entire API team — ops, IT, sysadmins, SREs and developers — stop blaming each other and work together.

I’ll cover accelerating API development by empowering your engineers, reducing incidents by simplifying deploys and moving toward continuous deployment by utilizing agile API development.


The 2016 Platform Summit


October 25, 2016 13:20