 Gianpaolo Carraro Platform Architecture Team Microsoft Corporation SYMP06

Code: How?Architecture: What/When? Business: Why? Session 1 Expanding Applications to the Cloud Session 2 Making Enterprise Grade Cloud Applications Session 3 Cloud or No Cloud, the Laws of Physics Still Apply

DG 13Developers Strongly Cautioned Limited Visual Studio Wizardry Some Excel Spreadsheet Usage RATING

Clearly Owning the pipe can offer an competitive advantage

Movie Service - Multicast and/or Peer to Peer top N (50?) movies - Use non IP network (e.g., cable for distribution) - End user read off local cache

source:

Source:

time failure rate "infant mortality" phase "constant failure rate" "wearout" phase MTBF = 1/constant failutre rate (does not take into account wear out phase, hence is not relevant for lifetime of a single component but very useful for average failure of many component) Example: A 30 years old in USA has a failure (death) rate of ~1.1 per 1000 MTBF of 900 years (actually person-years per death) Even the super healthy, organic eating person won’t reach that -> wear out phase

ConsistencyAvailability tolerance to network Partition

CAP C A P Consistency + Availability Single site / Cluster database C A P Consistency + Partition Distributed database / Distributed locking C A P Availability + Partition Distributed cache/ DNS

Sometimes, It’s OK to be wrong or down Compare cost of the apology vs. cost of knowing for sure

GOOD! Not so much!

“Exposed” for 22 months

Ouch!!

Still Ouch!! Still Ouch!!

Break Even but < 1% churn!?

French LecturerVisiting China Using a US-based Server Hosting 3 rd Party Service Caching data in Japan Rich Client Software Whose law applies where? What’s encrypted, and when? Who retains what information, and for how long? How does copyright apply to cached copies?

Please fill out your evaluation for this session at: This session will be available as a recording at:

© 2008 Microsoft Corporation. All rights reserved. Microsoft, Windows, Windows Vista and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries. The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.