[Microsoft][PDC][2009]SVC20.-.Bridging.the.Gap.from.On-Premises.to.the.Cloud

>SVC20Bridging the Gap From On-Premises to the Cloud Yousef KhalidiDistinguished EngineerWindows AzureOverview>Cloud opportunities and challenges>Spectrum from on-premises to cloud >Value for different points on spectrum>Framework for targeting apps to cloud >Questions to ask>Technology, tools, and approaches>Future-oriented presentationWhat is Cloud ComputingStyle of computing with dynamically scalable and virtualized resources provided as a service through the networkØ Cloud Application ModelØ Scale-outØ Service-orientedØ Model-drivenØApplicable to traditionalsystems and the cloudOpportunities and Challenges >Greater agility>Lower cost: CAPEX, OPEX>Targeting applications to thecloud>How to leverage on-premises,public, private and dedicatedclouds>Privacy of data>Connectivity>Latency/performanceconsiderationsTraditional DatacenterTraditional Datacenter >Well-known,stable and secure >Utilization <15%VirtualizedDatacenter>UtilizationIncreases to >50%>Management Costs DecreaseTraditional DatacenterPrivateCloud>ManagementCostsDecreaseSignificantly>Scale-outDevelopmentExpenseVirtualizedDatacenterPrivateCloudPublicCloud>Capacity onDemand>Global Reach VirtualizedDatacenter>UtilizationIncreases to >50%>ManagementCosts DecreaseTraditional DatacenterVirtualizedDatacenterPrivateCloudPublicCloudPublicCloud>Capacity onDemand>Global Reach BENEFITS OF CHOICEDEDICATED CLOUD PUBLIC CLOUDPRIVATE CLOUD Secure Cloud FederationINTERNAL ITENTERPRISEENTERPRISEDEDICATED CLOUDPUBLIC CLOUDPRIVATE CLOUDSecure Cloud FederationINTERNAL ITPUBLISH TO CLOUD OR ENTERPRISEThe Opportunity>Build rich applications for the cloud while preserving application symmetry withthe enterprise>Frictionless deployment across the spectrum >New breed of applications that span from on-premises to cloudQuestions to Consider>Is the application cloud-ready?ApplicationPortability>Are application dependencies met?ApplicationDependencies>Is application able to access required network resources?Connectivity>Are all other considerations met?Business andRegulationAnalyzing The Answers>In many cases, answers will not be clear Yes or No >The application could be a multi-tier service,>With mix of new cloud-ready code and existing code, >Where some components need to access resources in enterprise network,>Some components are chatty and latency sensitive,>And some of the application data may be subject to regulatory or other non-technical considerations.ProcessTopology Create blueprint with location of each compConsider business and regulatory issues CloudReadiness Make each component cloud-readyNew/modified or virtualized codeConnectivity Utilize connectivity, caching and sync techniquesConsider security and latency issuesManagement Deploy and monitorAcross locations per topologyApplication Portability>Newly developed applications>.NET and managed code technologies>State separated code>Model-driven deployment>Existing applications and components >Modifying apps when possible – meet the cloud half-way>Machine and applicationvirtualization technologiesExample: VM Support>Virtual Machine Role Type>Helps easily move existing apps to cloud>Enables wide range of Windows apps to run in Windows AzureApplication Dependencies>Making application code portable is only first step >Applications do not run in isolation>Need to access their data>Dependencies on run-time environments>Dependencies on network configuration>Dependencies on other servicesRequired Services and Connectivity >Increasing symmetry over time, e.g.,>SQL Server <-> SQL Azure>.Net +VS>Future – common models, end-to-end management >But required services may not be available >Options:1.Co-locate application with required services2.Access required services remotely>A combination of both options may be neededConnectivityData SynchronizationApplication ConnectivityServiceBusNetwork ConnectivityVirtual Network OverlayVirtualizing the NetworkPUBLIC CLOUDENTERPRISEPRIVATE CLOUD DEDICATED CLOUDSecure CloudFederation VIRTUAL NETWORK OVERLAYCloud NetworkBusiness and Regulations>Regulations and certifications>SOX, HIPPA, PCI, etc.>Business requirements>Company policies, IT policies, etc.>Such requirements must be considered early>Can affect basic topology of the service, location of data, communication patterns>Off-premises clouds over time will gain more certification >But the need to keep on-premises data and computation will not go awayPutting It All Together>Examine app components, and communication paths >Ask the questions listed before>Decide on the overall topology>Make the code cloud ready>New code should be written with cloud in mind>Consider modifying or using virtualization for existing code>Connect the components based on selected topology >Use various connectivity solutions as needed>Be careful with latency and communication boundaries >Make sure remote components are not chatty>Use caching and data sync as appropriate>Remember security, business, and regulatory requirements >At a minimum, these will affect overall topology of the serviceBeyond Bridging the Gap>Principles discussed enable moving apps to cloud >While bridging back to the enterprise>Current and future technologies for frictionless deployment and connectivity>Next: new transforming scenarios>Business continuity solutions>Collaboration scenarios>Extranet applications>Federation scenarios>…The Global Cloud>Secure GlobalOn-demandComputing>Always Available>Cloud Burstingand Load-balancing>Global Application Global Cloud Computingand Data DeliveryYOUR FEEDBACK IS IMPORTANT TO US!Please fill outsession evaluationforms online atLearn More On Channel 9>Expand your PDC experience through Channel 9>Explore videos, hands-on labs, sample code and demos through the new Channel 9training courses/learnBuilt by Developers for Developers….。