slide1 n.
Skip this Video
Loading SlideShow in 5 Seconds..
A ditee Rele Architect Evangelist PowerPoint Presentation
Download Presentation
A ditee Rele Architect Evangelist

Loading in 2 Seconds...

  share
play fullscreen
1 / 40
Download Presentation

A ditee Rele Architect Evangelist - PowerPoint PPT Presentation

kort
126 Views
Download Presentation

A ditee Rele Architect Evangelist

- - - - - - - - - - - - - - - - - - - - - - - - - - - E N D - - - - - - - - - - - - - - - - - - - - - - - - - - -
Presentation Transcript

  1. Cloud Computing Windows Azure™ Platform Overview • Aditee Rele • Architect Evangelist

  2. Agenda • Why the Cloud? • Azure Services Platform • Tour of the services

  3. Challenges Building Apps • # of users? After 1 month? 6 months? 1 yr? • Capacity? Servers? Bandwidth? Storage? • How do you scale up or down over time? • How can you handle peak loads? • How do you provide high availability? • What are the upfront capital costs? • How quickly can you go live? • How do you reduce your operations costs?

  4. Challenges Facing Today’s Enterprise 1 1 5 Infrastructure costs are fixed and ongoing, and distract from the mission of reducing business process friction Leveraging past investments to provide future value Many data centers at limit—real estate, capacity, cooling and power Matching capacity to demand Maintaining security while increasing access and transparency—within and outside the organization 2 6 Security, access, and transparency across the value chain: suppliers, partners, etc. 3 7 Lack of a common platform 4

  5. There are inefficiencies in addressing those issues Allocated IT-capacities Load Forecast “Under-supply“ of capacities “Waste“ of capacities Fixed cost of IT-capacities IT CAPACITY Barrier for innovations ActualLoad TIME

  6. What does an enterprise want to achieve? Load Forecast Allocated IT capacities No “under-supply“ IT CAPACITY Reduction of “over-supply“ Possible reduction of IT-capacities in case of reduced load Reduction of initial investments ActualLoad Time

  7. Cloud Computing “A pool of abstracted, highly scalable, and managed compute infrastructure capable of hosting end-customer applications and billed by consumption1” 1- “Is Cloud Computing Ready for The Enterprise?” Forrester Research, Inc.

  8. Why a Cloud Platform? Changing the Economics of Software • Reduce capital & operations costs • Simplify application deployment & management • Application & infrastructure flexibility • Simplify scaling to internet scale • Cost effectively handle peak loads • Focus on new functionality & not infrastructure

  9. Platform Continuum On-Premises Servers Hosted Servers Cloud Platform • Bring your own machines, connectivity, software, etc. • Complete control • Complete responsibility • Static capabilities • Upfront capital costs for the infrastructure • Renting machines, connectivity, software • Less control • Fewer responsibilities • Lower capital costs • More flexible • Pay for fixed capacity, even if idle • Shared, multi-tenant infrastructure • Virtualized and dynamic • Scalable and available • Abstracted from the infrastructure • Higher-level services • Pay as you go

  10. What are the attributes of a cloud platform? Accessed via the internet Third party provider • Low IT skill to implement • Self service, dynamic and fine-grained scaling • Usage based economics (CapEx to OpEx)

  11. Cloud Taxonomy

  12. The “Cloud” = 10X Improvements

  13. Time

  14. Scalability

  15. Reliability / Green

  16. Costs / Pricing

  17. Risk RISK

  18. Private Cloud? Traditional On-Premises Model Servers are dedicated to specific workloads Individual servers sized for peak or average capacity of a given workload Substantial idle/wasted capacity An application can’t scale beyond the boundaries of boxes it resides on Provisioning new capacity takes time Private Cloud Model Servers are treated as a virtual pool of resources Apps consume from the pool rather than having dedicated resources Idle servers automatically shut down or put to sleep until needed Apps can scale to the available provisioned capacity in the pool Adding a new server adds capacity to the entire pool for all apps Dedicated infrastructure (i.e., Cloud resources are only accessible to your company, and not shared with others)

  19. Benefits of Cloud Computing • Flexible resources such as compute and storage • Add and remove capacity on demand • Pay for what you consume rather than provision to peak • Shift administration boundary • Focus on ‘what’ and not ‘how’ • Separate physical and logical administration • Software and services integration • Get the most out of your on-premises investments • Implement scenarios not possible through only on-premises or cloud

  20. On-Premises Cloud Services Visual Studio & .NET “Oslo” - Modeling Partner Ecosystem

  21. Cloud Services Web and Clouds Developer Experience Web applications Third party Cloud Use existing skills and tools. Compute Storage Management Relational data Management Connectivity Access control On-premises Composite applications LOB Applications

  22. Windows Azure • Operating System for the Cloud • Platform that can manage connected Hardware • Share Resources

  23. From Managing Resources to Providing Abstraction BUSINESSES CONSUMERS INTERNET

  24. The Azure Fabric Interacts with a “Fabric Agent” on each machine Monitors every VM, application and instance Performs load balancing, check pointing and recovery

  25. Fabric controller Fabric Compute Storage Fabric controller Geographically distributed, state-of-the-art data centers. Security and Control Features

  26. Compute in Windows Azure SCALABILITY Scale out by replicating worker instances as needed. Allow applications to scale user and compute processing independently. Two instance types: Web Role & Worker Role Windows Azure applications are built with web role instances, worker role instances, or a combination of both. Each instance runs on its own VM (virtual machine), replicated as needed

  27. Defining the Web and Worker Roles WEB ROLE WORKER ROLE Interacts with end-user or web services Handles incoming HTTP/HTTPS requests Develop with Microsoft and non-Microsoft tools: ASP.NET, WCF, other .NET tools Java, PHP, etc. Does not accept incoming requests Initiates their own requests for data or tasks from the queue Similar to a "batch job" or Windows service

  28. Windows Azure Storage Blobs, Tables and Queues BLOBS: Provide a simple interface for storing named files along with file metadata QUEUES: Provide reliable storage and delivery of messages for an application TABLES: Provide structured storage. A Table is a set of entities which contain a set of properties

  29. Windows Azure Storage SCALABLE, DURABLE STORAGE Tables: simply structured data, accessed using ADO.NET Data Services Queues: serially accessed messages or requests, allowing web-roles and worker-roles to interact Blobs: large, unstructured data (audio, video, etc) Windows Azure storage is an application managed by the Fabric Controller Windows Azure applications can use native storage or SQL Azure Application state is kept in storage services, so worker roles can replicate as needed

  30. Services Management -AUTOMATED APPLICATION MANAGEMENT AND CONTROL Fabric The Fabric Controller automates service management

  31. Building Solutions with the Windows Azure Platform SQL Azure: Scalable, relational, Cloud-enabled database services .NET Services: Framework for access control and communication between Cloud-aware applications

  32. Providing Security with Windows Azure • PHYSICAL: • Microsoft data centers with modern and current security processes • Redundant power supplies from separate providers, battery and diesel backup generators, climate control, and fire prevention and suppression • CONTINUITY: • Multiple data centers in different geographies • Users can choose single location or geo-distributed data centers • Storage data is replicated multiple times • Fabric is designed to be backed up and restored from checkpoints • COMPLIANCE & CERTIFICATION: • Microsoft is committed to complying with all local laws • Industry certification is a core part of the Windows Azure roadmap • Customers are ultimately responsible for the security and compliance of their services or applications–Windows Azure is a platform • LOGICAL: • Storage encryption and authentication • HTTPS • Optimized for Cloud access with no admin access to guests or applications • Applications and users not allowed to update the underlying environment

  33. Windows Azure platform Example Scenarios • Brand Website • Gaming Platform (Xbox Live, EA) • Blog Platform (WordPress) • Real-time media streaming (radio, TV) • Stored media streaming distribution (podcast) • Social Networking (Facebook, MySpace.com) Scalable Web-Apps (Web) • Net New • Application / Service • E-Market Platform (eBay, Craigslist) • E-Shopping (Buy.com) • IT enabled sales force for Pharma • Channel integration and customer management for retail • Electronic payment platform for Financial Services • Payroll • Supply and distribution for Transportation • Collaboration and knowledge management • Productivity suite platform • Customer inquiries (Customer Service) • Accounts payable / receivable • Collaborative R&D environment for Pharma Scalable Multi- Channel Apps (Middle-tier, OLTP) • Optimizing • Existing • Application / Service • Digitization of Media • E-Discovery (Analytics) • Media trans-coding & post-processing • Combinatorial drug analysis/research Compute Storage (Archiving) • Back-ups • Archiving – Cold

  34. Developing Applications for Windows Azure FAMILIAR DEVELOPER EXPERIENCE DESIGNED FOR INTEROPERABILITY PROVEN MICROSOFT TECHNOLOGIES Development: Visual Studio integration, offline Cloud simulation Maintenance: Local debugging, APIs for logging Management: APIs for configuration management SOAP and REST protocols XML file formats Commitment to support Java, PHP, Python and other popular programming languages Visual Studio, ASP.NET, SQL Azure integration Windows Azure integration

  35. Windows Azure Platform Service Guarantee • Storage servicewill be available/ reachable (connectivity) • Your storage requests willbe processed successfully • .NET Service Bus endpoint willhave external connectivity • Message operation requests willbe processed successfully Serviceavailability Storage availability Database availability • Role instance monitoring and restart Compute connectivity All runningroles will be continuously monitored If role is unhealthy, we will detect and initiate corrective state Your service is connected and reachable via web Internet facing roles will have external connectivity Database is connected to the internet gateway Availability monitoring every 5-minute interval Automated Systems Management >99.9% >99.95% >99.9% >99.9%

  36. Azure Summary • Comprehensive cloud services platform • Abstracts you from the infrastructure • Flexibility to mix & match services • Connectivity to on-premises environments • Familiar programming model & tools • Rich client experiences with Live Services • Standard protocols & formats (HTTP, REST, ...)

  37. Learning Windows Azure • www.azure.com • Download the SDK • You don’t need cloud access to develop! • Look at the samples in the SDK • Azure Services Training Kit • Follow the team bloggers http://www.azure.com http://www.thecloudapp.net

  38. Resources Azure Services Training Kit Downloadable hands-on labs, demos, and presentations http://www.azure.com Azure Services Platform Forums http://www.microsoft.com/azure/blog.mspx Azure Whitepapers http://www.microsoft.com/azure/whitepaper.mspx

  39. © 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.