The document outlines 7 rules for cloud-native development according to Solomon Hykes: 1. Think in terms of services rather than servers 2. Don't reinvent the wheel and leverage existing services 3. Avoid silos and have integrated, cross-functional teams working on products 4. Don't impose unnecessary restrictions that get in the way of developers 5. Start with standardized approaches and only customize later if needed 6. Enable rapid experimentation through a service-oriented architecture 7. Ship code changes daily to maximize speed and productivity

1. Solomon Hykes

2. We make
developers
productive

3. Being a developer
in 2013

4. Being a developer
in 2013
is awesome

5. Software is
eating the world

6. speed
=
victory

7. Developer productivity
=
speed

8. HOW?

9. 7 rules
of cloud-native
development

10. 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

11. 1.
Think services, not servers

12. Your last app

13. Your next app

14. Services are libraries
that run themselves

15. 2.
Don’t reinvent the wheel

17. What differentiates you?

18. Focus

19. Focus
Outsource the rest

20. Justin Kan
CEO, Exec
“Without these ready-to-use cloud services
we never could have launched so fast with a
team so small”

21. 3.
Don’t create silos

22. Web DBA Ops Systems

23. Web DBA Ops Systems

24. Product A
Product B
Product C

25. One team per product
One product per team
Run what you write

26. 4.
Don’t get in the way
of the developer

27. Functional
requirements
Technical
requirements
“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”

28. 5.
Cookie-cutter first,
customize later

29. Scott Vandenplas
Lead 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 a
waste of precious time.”

30. 6.
Experiment quickly

31. Isaac Wolkerstorfer
CTO, 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”

32. 7.
Ship every day

33. 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

34. It’s all about
speed

35. It’s all about
developer productivity

36. Thank you!