Upload
docker-inc
View
64
Download
2
Tags:
Embed Size (px)
Citation preview
1. Think services, not servers
2. Don’t reinvent the wheel
3. Don’t create silos
4. Don’t get in the way of the developer
5. Cookie-cutter first, customize later
6. Experiment quickly
7. Ship every day
Justin KanCEO, Exec
“Without these ready-to-use cloud services we never could have launched so fast with a team so small”
Functionalrequirements
Technicalrequirements
“It has to work for 100,000 simultaneous connections”
“We need to go Live by Christmas”
“It has to pass next quarter’s infosec audit”
“This can’t go down during next week’s demo. Do
whatever it takes”
“It has to be Java”
“If you need more servers, ask Bob for it and wait”
“I heard Node.js is the future, rewrite it all in Node.js”
“Your performance will be measured by the number of
lines of code written”
Scott VandenplasLead devops, Obama for America
“We started monitoring with plain old Nagios.Not perfect but familiar and reliable.”
“Once we hit scale problems, we located the bottleneck (NRPE) and replaced it with ZERORPC”
“It’s still Nagios, with just enough customization. Investing that time upfront would have been awaste of precious time.”
Isaac WolkerstorferCTO, 6Wunderkinder
“1 million users in 9 months. How do we keep shipping fast without breaking?”“Service-oriented means we choose the best tool for each feature.”“I can use Ruby for one service and PHP for another. I only refactor when I decide to”
Start Shipping on Day 1.Don’t wait for the launch!
Replicate your stack in a sandbox that mirrors the production environment.Deploy to that sandbox every day.Give each developer his own sandbox