Windows Azure For Architects

763 views
696 views

Published on

A presentation which provides a Windows Azure overview, targeted at software architects

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

  • Be the first to like this

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

No notes for slide

Windows Azure For Architects

  1. 1. Windows Azure for Architects Anko Duizer February 6nd 2010
  2. 2. Introducing… • Anko Duizer – Chief Software architect – Blog: http://www.ankoduizer.nl – Twitter: ankoduizer • TellUs – Lead generation – > 5000 sites – World wide – Microsoft platform
  3. 3. Introduction
  4. 4. Cloud computing is Internet ("cloud") based development and use of computer technology ("computing”)
  5. 5. Cloud Attached platforms IaaS services SaaS (PaaS) Extra Application Cloud ? Application functions Platform On- Browser/ ? Application client Application premises
  6. 6. Storage Integration Development environment Identity Management Application Infrastructure services Local support Operating system Applications Foundation Application services
  7. 7. Cloud From on-premises to cloud platforms Cloud infrastructure application services Cloud foundation Cloud application services On-premises On-premises infrastructure application services OS On-premises application services
  8. 8. Part 1: Windows Azure Platform
  9. 9. Windows Azure platform AppFabric Applications SQL Azure Windows Azure Live Services Applications Windows Windows 7/ Windows Others Server Vista/XP Mobile
  10. 10. Application Compute Storage Config Fabric
  11. 11. HTTP Blobs Tables Queues
  12. 12. Access Control (ACS) ? Service Bus
  13. 13. 2) Discover endpoints Service bus Registry 1) Register 3) Access Endpoints endpoints application Application Application Organization X Organization Y
  14. 14. SQL Data Services Others (future)
  15. 15. Windows Azure service lifecycle Coding and Provisioning Deployment Maintain modeling goal state - Mapping and deploying to - Monitor New services Desired actual - React to configuration hardware events and updates - Network configuration Developer Developer/ Automated Automated Deployer
  16. 16. Part 2: Basic principle
  17. 17. Simplicity
  18. 18. Part 3: Architecture principles
  19. 19. Hardware fails
  20. 20. A few design choices
  21. 21. Big, reliable, expensive machine
  22. 22. Several commodity machines
  23. 23. Lots and lots of commodity machines
  24. 24. A few challenges
  25. 25. What do you do about that thing called state?
  26. 26. Go horizontal Go stateless
  27. 27. Store state in Windows Azure storage
  28. 28. How do you deal with unreliable components?
  29. 29. Default.aspx Worker.cs LB (web role) (worker role) Queue
  30. 30. Public Internet Web role LB Storage services
  31. 31. Public Internet Worker role Storage services
  32. 32. Be loosely coupled
  33. 33. Use Windows Azure queues for separation of work
  34. 34. How do you deal with varying load?
  35. 35. How do you deal with failures?
  36. 36. Use Windows Azure storage for valuable data
  37. 37. ... Entity Entity Entity ... Property Property Property Name Type Value
  38. 38. What about the SQL Azure?
  39. 39. Application Application Browser ODBC, OLEDB, application REST Client SQL Client* ADO.Net PHP, Ruby, … Cloud HTTP+REST HTTP TDS Windows Azure REST (Astoria) Web App Data center ADO.Net + EF SQL Client* TDS + TSQL Model SQL Azure
  40. 40. Cloud Data in the application cloud On-premises application
  41. 41. Retry on transient failures But…
  42. 42. Be idempotent
  43. 43. Part 4: Managing
  44. 44. Production Stage Deployment Deployment
  45. 45. +
  46. 46. Future: Precise control
  47. 47. How do I debug the cloud?
  48. 48. Logging
  49. 49. How do I get notified when something bad happens?
  50. 50. ! Windows Azure’s alerts
  51. 51. Part 4: Useful?
  52. 52. “On and Off “ “Growing Fast“ Compute Compute Inactivity Period Average Usage Average Usage Time Time On & off workloads (e.g. batch job) Successful services needs to grow/scale Over provisioned capacity is wasted Keeping up w/ growth is big IT challenge Time to market can be cumbersome Complex lead time for deployment “Unpredictable Bursting“ “Predictable Bursting“ Compute Compute Average Usage Average Usage Time Time Unexpected/unplanned peak in demand Services with micro seasonality trends Sudden spike impacts performance Peaks due to periodic increased demand Can’t over provision for extreme cases IT complexity and wasted capacity
  53. 53. Is it cheaper?
  54. 54. Compute : $0.12 / hour Storage : $0.15 GB / month Bandwidth: $0.10 GB in, $0.15 GB out
  55. 55. Retry on failures Recap Loose coupling

×