1 / 40

Cloud Computing – Who Wins, Who Loses, How to survive

Cloud Computing – Who Wins, Who Loses, How to survive. Jim Wilt Chief Software Architect Metrics Reporting, Inc. 2010 jim.wilt@metricsreporting.com (616) 617-3775. Goals from this talk…. Common understanding of what Cloud Computing actually is

les
Download Presentation

Cloud Computing – Who Wins, Who Loses, How to survive

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Cloud Computing – Who Wins, Who Loses, How to survive Jim Wilt Chief Software Architect Metrics Reporting, Inc. 2010 jim.wilt@metricsreporting.com (616) 617-3775

  2. Goals from this talk… • Common understanding of what Cloud Computing actually is • How to circumvent push-back through increased competencies in your knowledge of cloud architectures(Maybe you’re pushing back? Let’s change that!) • Where to focus your architectural efforts to shape Cloud Computing

  3. Above the Clouds: A Berkeley View of Cloud Computing Alan Hakimi Andy Catlin Andy Ruth Clayton Christensen’s The Innovator’s Dilemma David Chappell Miha Kralj Norm Judah Pallaw Sharma Pat Helland Richard Webb Ryan Dunn Scott Andersen Simon Guest Riding on the Shoulders of Giants… This material is a culmination from the great efforts of:

  4. Looking Backward to see Forward… Can I really see the future by looking back?

  5. 1980

  6. 1980 With great uncertainty, Enterprises enter the PC era

  7. 1995

  8. 1995 With great uncertainty, Enterprises enter the Internet era

  9. 2010

  10. 2010 With great uncertainty, Enterprises contemplate the cloud

  11. What Really is the Cloud Anyway? What’s The Future (WTF)?

  12. What the Cloud IS NOT (though some claim it is)… • Consolidation + Virtualization - Licenses (let’s beat the system) • Outsourced Infrastructure • Hosted SOA Services (although they may be used in cloud solutions)

  13. What the Cloud IS (in terms of existing technologies)… • GRID + SOA + Fabric • Elastic Computing • Simple “pay as you go model” A cloud architecture is a solution delivery method that embodies elastic infrastructure to respond dynamically to demand

  14. Today’s Data Center… 100% Capacity (what I pay for) 85% Capacity (most I can use) My Infrastructure My utilization over time

  15. Today’s Data Center - by the Numbers $1.50/CPU Hour $1.76/CPU Hour Net $1500/Day for 850 Max CPU Hours $1500/Day for 420 CPU Hours Used

  16. Cloud Computing… Unlimited CapacityInfrastructure My utilization over time High Availability via Replication/Duplication

  17. Cloud Computing - by the Numbers $2.25/CPU Hour $945 for 420 CPU Hours Used

  18. Private Clouds…

  19. 1985

  20. 1985 The Irma Card was the crutch the Enterprise used to adopt the PC

  21. Private Clouds… An unfortunate necessity to pacify the enterprise while cloud security matures

  22. What are the Cloud Application Models? • How do I choose?

  23. So, then, Who Wins & Who Loses? • How about another flash-back?

  24. 1980

  25. 1980

  26. 1995

  27. 1995

  28. 2010

  29. 2010 Compromisebreedsmediocrity…

  30. Mitigating Pushback • Fight fire with soothing water… The best response in these situations will come from well grounded understanding of what the cloud and its cost structure really is

  31. Our systems don’t need to be elastic, they run at a steady level Mitigating Pushback… • One event can cause unexpected burden on any system, even impact the entire internet • The cloud is also about redundancy (data in triplicate) eliminating backups and increased availability • No different than: • Doesn’t need to be fast, just needs to work… • We’ll go back and add documentation later… • This hard-coded prototype won’t become production… • We will be a paperless office by year's end...

  32. We’ll all lose our jobs when we move the data center to the cloud Mitigating Pushback… • The cloud is complicated and will need every [willing] resource • Your attitude and drive have as much if not more effect • Your value is reflected in your willingness to make your organization successful

  33. How to Survive… • First & foremost, invest in yourself

  34. Live, Breathe, and Be David Chappell’s papers & Ryan Dunn’s presentations thoroughly understanding each component How to Survive – Establish Competency in the Platform http://www.microsoft.com/windowsazure/getstarted/

  35. How to Survive – Establish Competency in the Costs Understand and model the financials

  36. How to Survive – Establish Competency in Alignment of Tipping Points Model, Prototype, and Build Elasticity based on multiple thresholds/triggers • Performance • Capacity • Demand/Load • Financial

  37. How to Survive – Establish Competency in the Unknowns Push the threshold for Cloud Concepts • Consider encrypting data prior to cloud storage • Build your own self-health monitoring & reporting systems • Experiment with various approaches to state management • Build a framework that gives your organization a competitive advantage

  38. How to Survive – Combine Resources into Dream Teams Cloud solution teams should be a balance of historical Infrastructure and Solutions resources working in tandem Solutions/Dev GreatCloudValue Infrastructure

  39. Call to Action Go, experiment, learn, fail, and shape the cloud! The only satisfaction a pioneer secures is that of when they first discover an untold truth in nature or science for which their own eyes behold…

More Related