World of Services: The Software Architecture that is Eating the World

1,553 views

Published on

dotCloud CEO Solomon Hykes explores the seven rules of cloud native development in the World of Services Keynote, Up Cloud Computing Conference 2012
Marc Andreessen discussed the reasons why he thinks software is eating the world, where an online software services takes over the market from a traditional brick and mortar incumbent.
Solomon Hykes believes a similar phenomenon is happening in software, in which cloud native development is eating up traditional software architectures.

More info: https://www.dotcloud.com/

0 Comments
5 Likes
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total views
1,553
On SlideShare
0
From Embeds
0
Number of Embeds
1
Actions
Shares
0
Downloads
18
Comments
0
Likes
5
Embeds 0
No embeds

No notes for slide

World of Services: The Software Architecture that is Eating the World

  1. 1. Solomon Hykes
  2. 2. We makedevelopersproductive
  3. 3. Being a developerin 2013
  4. 4. Being a developer in 2013is awesome
  5. 5. Software iseating the world
  6. 6. speed =victory
  7. 7. Developer productivity = speed
  8. 8. HOW?
  9. 9. 7 rulesof cloud-native development
  10. 10. 1. Think services, not servers2. Don’t reinvent the wheel3. Don’t create silos4. Don’t get in the way of the developer5. Cookie-cutter first, customize later6. Experiment quickly7. Ship every day
  11. 11. 1.Think services, not servers
  12. 12. Your last app
  13. 13. Your next app
  14. 14. Services are librariesthat run themselves
  15. 15. 2.Don’t reinvent the wheel
  16. 16. What differentiates you?
  17. 17. Focus
  18. 18. est e r e th urc ts oOu Focus
  19. 19. Justin Kan CEO, Exec“Without these ready-to-use cloud serviceswe never could have launched so fast with ateam so small”
  20. 20. 3.Don’t create silos
  21. 21. Web DBA Ops Systems
  22. 22. Web DBA Ops Systems
  23. 23. Product AProduct BProduct C
  24. 24. One team per productOne product per teamRun what you write
  25. 25. 4.Don’t get in the way of the developer
  26. 26. Functional Technical requirements requirements“It has to work for 100,000 “It has to be Java”simultaneous connections” “If you need more servers, ask “We need to go Live by Bob for it and wait” Christmas” “I heard Node.js is the future,“It has to pass next quarter’s rewrite it all in Node.js” infosec audit” “Your performance will be“This can’t go down during measured by the number of next week’s demo. Do lines of code written” whatever it takes”
  27. 27. 5.Cookie-cutter first, customize later
  28. 28. 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 awaste of precious time.”
  29. 29. 6.Experiment quickly
  30. 30. Isaac Wolkerstorfer CTO, 6Wunderkinder“1 million users in 9 months. How do we keep shippingfast without breaking?”“Service-oriented means wechoose the best tool for each feature.”“I can use Rubyfor one service and PHP for another. I only refactorwhen I decide to”
  31. 31. 7.Ship every day
  32. 32. Start Shipping on Day 1. Don’t wait for the launch!Replicate your stack in a sandbox that mirrorsthe production environment.Deploy to thatsandbox every day.Give each developer his ownsandbox
  33. 33. It’s all about speed
  34. 34. It’s all aboutdeveloper productivity
  35. 35. Thank you!

×