1 / 27

Bridging the Gap From On-Premises to the Cloud

SVC20. Bridging the Gap From On-Premises to the Cloud. Yousef Khalidi Distinguished Engineer Windows Azure . Overview. 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

aine
Télécharger la présentation

Bridging the Gap From On-Premises to the Cloud

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. SVC20 Bridging the Gap From On-Premises to the Cloud Yousef Khalidi Distinguished EngineerWindows Azure

  2. Overview • 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 presentation

  3. What is Cloud Computing Style 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 traditional systems and the cloud

  4. Opportunities and Challenges • Greater agility • Lower cost: CAPEX, OPEX • Targeting applications to the cloud • How to leverage on-premises, public, private and dedicated clouds • Privacy of data • Connectivity • Latency/performance considerations

  5. Spectrum Extending Into the Cloud TraditionalDatacenter VirtualizedDatacenter TraditionalDatacenter • Well-known, stable and secure • Utilization <15% • Utilization Increases to >50% • Management Costs Decrease

  6. Spectrum Extending Into the Cloud PrivateCloud Public Cloud VirtualizedDatacenter VirtualizedDatacenter PrivateCloud TraditionalDatacenter • Utilization Increases to >50% • Management Costs Decrease • Capacity on Demand • Global Reach • Management Costs Decrease Significantly • Scale-out Development Expense

  7. Spectrum Extending Into the Cloud Public Cloud VirtualizedDatacenter PrivateCloud PublicCloud TraditionalDatacenter BENEFITS OF CHOICE • Capacity on Demand • Global Reach

  8. The Cloud DEDICATED CLOUD PUBLIC CLOUD Secure CloudFederation ENTERPRISE PRIVATE CLOUD INTERNAL IT

  9. The Cloud DEDICATED CLOUD PUBLIC CLOUD PUBLISH TO CLOUDOR ENTERPRISE Secure CloudFederation ENTERPRISE PRIVATE CLOUD INTERNAL IT

  10. The Opportunity • Build rich applications for the cloud while preserving application symmetry with the enterprise • Frictionless deployment across the spectrum • New breed of applications that span from on-premises to cloud

  11. Application Portability Questions to Consider • Application Dependencies • Is the application cloud-ready? • Connectivity • Are application dependencies met? • Business and Regulation • Is application able to access required network resources? • Are all other considerations met?

  12. Analyzing 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.

  13. Process • Create blueprint with location of each comp • Consider business and regulatory issues • Topology • Cloud • Readiness • Make each component cloud-ready • New/modified or virtualized code • Utilize connectivity, caching and sync techniques • Consider security and latency issues • Connectivity • Deploy and monitor • Across locations per topology • Management

  14. Application 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 application virtualization technologies

  15. Example: VM Support • Virtual Machine Role Type • Helps easily move existing apps to cloud • Enables wide range of Windows apps to run in Windows Azure

  16. Application 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 services

  17. Required 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: • Co-locate application with required services • Access required services remotely • A combination of both options may be needed

  18. Connectivity Data Synchronization Application Connectivity ServiceBus Network Connectivity Virtual Network Overlay

  19. Virtualizing the Network VIRTUAL NETWORK OVERLAY ENTERPRISE DEDICATED CLOUD PRIVATE CLOUD PUBLIC CLOUD Cloud Network Secure CloudFederation

  20. Business 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 away

  21. Putting 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 service

  22. Beyond 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 • …

  23. The Global Cloud • Secure Global On-demand Computing • Always Available • Cloud Bursting and Load-balancing • Global Application and Data Delivery Global Cloud Computing

  24. YOUR FEEDBACK IS IMPORTANT TO US! Please fill out session evaluation forms online at MicrosoftPDC.com

  25. Learn More On Channel 9 • Expand your PDC experience through Channel 9 • Explore videos, hands-on labs, sample code and demos through the new Channel 9 training courses channel9.msdn.com/learn Built by Developers for Developers….

More Related