Architecting Organizations for the Cloud

705 views

Published on

Video and slides synchronized, mp3 and slide download available at URL http://bit.ly/1mhidBi.

Sebastian Stadil advises on selecting the right cloud from EC2, GCE, or OpenStack based on one's needs, outlining the deployment and administrative challenges to be faced with each option. Filmed at qconsf.com.

Sebastian Stadil is a seasoned entrepreneur based out of San Francisco. He founded Silicon Valley’s Cloud Computing Group and contributes to journals such as InfoQ, Conversations Network, Internet Evolution, and Silicon Angle. His work has been featured in Wired Enterprise, TechCrunch, The Register, Businessweek, GigaOM, and Network World.

Published in: Technology, Business
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
705
On SlideShare
0
From Embeds
0
Number of Embeds
2
Actions
Shares
0
Downloads
0
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

Architecting Organizations for the Cloud

  1. 1. Architecting Organizations for the Cloud
  2. 2. Watch the video with slide synchronization on InfoQ.com! http://www.infoq.com/presentations /cloud-organization-architecture InfoQ.com: News & Community Site • 750,000 unique visitors/month • Published in 4 languages (English, Chinese, Japanese and Brazilian Portuguese) • Post content from our QCon conferences • News 15-20 / week • Articles 3-4 / week • Presentations (videos) 12-15 / week • Interviews 2-3 / week • Books 1 / month
  3. 3. Presented at QCon San Francisco www.qconsf.com Purpose of QCon - to empower software development by facilitating the spread of knowledge and innovation Strategy - practitioner-driven conference designed for YOU: influencers of change and innovation in your teams - speakers and topics driving the evolution and innovation - connecting and catalyzing the influencers and innovators Highlights - attended by more than 12,000 delegates since 2007 - held in 9 cities worldwide
  4. 4. Architecting Organizations for the Cloud
  5. 5. Architecting Organizations for the Cloud
  6. 6. SITUATION
  7. 7. Transitioning to the Cloud • New organizations have it easy • Real challenge is existing ones • Especially in the Enterprise
  8. 8. COMPLICATION
  9. 9. IT objectives != BU objectives
  10. 10. IT objectives • Keeping BUs productive • Leverage economies of scale • Define & enforce policies
  11. 11. BU objectives • Reducing time to market • Facilitating experiments • Reducing cost of failure
  12. 12. Trading off between security and convenience means trading off aforementioned objectives.
  13. 13. Historical failures of IT • Stem from procurement process • Build vs buy
  14. 14. Buy • UX never a criteria. • Managing supplier risk leads to big shops.
  15. 15. Build • No competition • Best developers go product.
  16. 16. Different levels of risk aversiveness
  17. 17. Selecting for a culture • New teams (i.e., Netflix) have selected for a certain culture • Risk tolerance & cloud familiarity • An Enterprise can't do this easily
  18. 18. Pets vs cattle • Traditionally, servers are managed like pets • In Cloud Native architectures, servers are managed like cattle
  19. 19. Evidence • Private clouds built as on-demand VPS • Used for self-service, not for Cloud Native • Management tactics different
  20. 20. Cost of wrongful shutdown >> savings from shutdown
  21. 21. IMPLICATION
  22. 22. Politics & tensions
  23. 23. Politics • Who's job is going to be made easiest? • Effort diverted away from customers
  24. 24. Rebellion & Rogue IT
  25. 25. New Problems • Incomplete picture • Genentech story • Risks, legal and other
  26. 26. Private cloud purposes
  27. 27. Private cloud • Built to accommodate wrong pet / cattle type • Repatriation breaks applications • API-compatible yet broken portability
  28. 28. SOLUTIONS
  29. 29. No silver bullet– Awareness is a first step
  30. 30. Identify type of workload • Pet or cattle? Is everyone on the same page about this? • Elastic? Regulated? Offered to customers, or for internal use? • What's the application lifecycle? Oneoff development, or continuously improved? • Special orchestration or not?
  31. 31. Picking the right cloud
  32. 32. From Amazon to Terremark • Amazon tries hard to accommodate pets & cattle • Private cloud accommodates your use case • Terremark keeps your instances on quality hardware
  33. 33. QUESTIONS
  34. 34. TAKEAWAYS
  35. 35. Driving fast vs driving slow
  36. 36. Disaster recovery > disaster avoidance • Sometimes no choice: app can't be rewritten, tech stack doesn't support it • Tooling needs to accommodate both mindsets • Scalr learned this the hard way
  37. 37. THANK YOU!
  38. 38. Watch the video with slide synchronization on InfoQ.com! http://www.infoq.com/presentations/cloudorganization-architecture

×