Windows Azure Alex BOGDAN Academic Developer Evangelist

Evolution towards highly virtual and beyond to cloud

what is the challenge with current applications?

Application Software: Web Servers, Databases, Messaging, Workflow… HARDWARE: Servers, Switches, Load Balancers etc… Application: Business Logic, Code & Data EACH APPLICATION: Many hardware & software components to install, configure, manage Hardware and Software is dedicated to the Application Scaled and Architected for Worst Possible Case Always ON Multiple environments – Dev, Test, pre-Prod, Prod Operating Software: Networking, Storage, Compute… EXPENSIVE IN-FLEXIBLE UNDER UTILIZED BRITTLE TAKES TOO LONG

target.com walmart.com toysrus.com barnesandnoble.com Source: Alexa ~4x normal load (Holiday shopping) turbotax.com taxcut.com hrblock.com taxact.com ~10x normal load (Tax season) Source: Alexa

Compute High Constant Usage Stable High Volume Successful application that is constantly used at high capacity but growth is limited and application meets all needs Server/Software Cost Predictable Bursting Services with micro seasonality trends Peaks due to periodic increased demand IT complexity and wasted capacity Server/Software Cost Unpredictable Bursting Unexpected/unplanned peak in demand Sudden spike impacts performance Can’t over provision for extreme cases Server/Software Cost Growing Fast Successful services needs to grow/scale Keeping up w/ growth is big IT challenge Cannot provision hardware fast enough Server/Software Cost On and Off On & off workloads (e.g. batch job) Over provisioned capacity is wasted Time to market can be cumbersome Server/Software Cost Total Cost on Separate Hardware WHAT IF… We could share the hardware and the software across applications, across organizations… We could scale up/down to closely match application needs & pay only for what I am using… Resilience was baked in Building applications was easier Cost Saving Server/Software Cost Server/Software Cost For BOTH systems + Costs to make systems resilient Predictable Bursting Services with micro seasonality trends Peaks due to periodic increased demand IT complexity and wasted capacity Server/Software Cost

sharing hardware AND software is where we want to be… how…?

OPERATING SYSTEM (Windows) VIRTUALIZATION (Hyper-V) Virtual Machine A file on a disk – the physical machine became a software representation Hyper-V understands and runs this file VM’s configured against the physical resources You install an OS and all needed software in the VM VM CPUmemorydisknetwork dedicated to VMsshared across VMs

EACH APPLICATION: Is a collection of Virtual Servers run on Shared Hardware ON when needed, OFF when not Physical resources can be optimized VM’s are portable, easily moved, copied IT Ops becomes automated, faster, cheaper Software can provision, mange and control WHAT IF… -> We could share on a massive scale… -> Share across companies and even geographies…? TO START: WE WOULD NEED DIFFERENT DATA CENTERS OPERATING SYSTEM (Windows) VIRTUALIZATION (Hyper-V) VM (Machine C) VM (Machine A) VM (Machine B) VM (Machine D) VM (Machine E) VM (Machine I) VM (Machine F) VM (Machine G) VM (Machine J) VM (Machine H) VM (Machine K) Hyper-V Manager System Center the private cloud

Videos Data Center Innovation

San Antonio, TX Approx 477K sq ft, 27MW, uses recycled water for cooling Chicago, IL 707,000 square feet with critical power of 60 MW, uses water side economization, containers Dublin, Ireland Approx 570K sq ft, up to 27MW, uses outside air for cooling. Green Energy

everything in Windows Azure is virtual (well almost…)

On Premises Storage Servers Networking O/S Middleware Virtualization Data Applications Runtime You manage Infrastructure (as a Service) Storage Servers Networking O/S Middleware Virtualization Data Applications Runtime Managed by vendor You manage Platform (as a Service) Managed by vendor You manage Storage Servers Networking O/S Middleware Virtualization Applications Runtime Data Software (as a Service) Managed by vendor Storage Servers Networking O/S Middleware Virtualization Applications Runtime Data

Windows Azure Fabric Controller Understands the physical DC – servers, load balancers, networking etc. Interacts with the OS on the physical machines and manages all aspects of virtual machines Multiple fabric controllers work together Four main responsibilities: Datacenter resource allocation Datacenter resource provisioning Service lifecycle management Service health management Virtual Machine Power on & Configure virtual server Power on & Configure virtual server

Infrastructure as a Service: You Build/Upload Virtual Machines to a DC on the Internet – e.g. Windows Azure You PAY for time/resources used and the software in your VM’s Your virtual machines RUN on hardware shared with other organizations You manage ALL aspects of the software stack inside your virtual machines VM’s can be moved to/from the Cloud and your own data center App development is unchanged VM Library: Pre-Built O/S + App Services or your own supplied VM Provisioning, Billing, Management Web Portal, self-service provisioning Windows Azure Fabric Controller Software that manages the physical infrastructure, O/S resources and virtual machines at Global DC scale

IaaS/Virtualization – Can we do even more..?

On Premises Storage Servers Networking O/S Middleware Virtualization Data Applications Runtime You manage Infrastructure (as a Service) Storage Servers Networking O/S Middleware Virtualization Data Applications Runtime Managed by vendor You manage Platform (as a Service) Managed by vendor You manage Storage Servers Networking O/S Middleware Virtualization Applications Runtime Data Software (as a Service) Managed by vendor Storage Servers Networking O/S Middleware Virtualization Applications Runtime Data

Windows Azure BLOB Storage Example You SUBSCRIBE to the service and create a unique name You GIVE Blobs(Files) to the Storage Service – simple API or REST The service provides resilience and scale, you don’t have to. You ask for them back – you don’t care or know where they really are (which VM’s) The service and the fabric controller make sure your data is stored so there is no single point of failure You pay for the amount of storage you use - the service manages everything The service can also geo-replicate, provide disaster recovery Windows Azure Data Center (e.g. North Central U.S) Windows Azure Fabric Controller VM ?

With PaaS – You don’t see VM’s Application package contains all the application artifacts – code, schema, data etc. The PaaS services and the fabric controller take care of deploying your app across the services you use Each Service (database, messaging, web etc.) provides scale and resilience capabilities for your apps Virtual Machine Application Package Power on & Configure virtual server Power on & Configure virtual server Instances = 2

On Premises Storage Servers Networking O/S Middleware Virtualization Data Applications Runtime You manage Infrastructure (as a Service) Storage Servers Networking O/S Middleware Virtualization Data Applications Runtime Managed by vendor You manage Platform (as a Service) Managed by vendor You manage Storage Servers Networking O/S Middleware Virtualization Applications Runtime Data Software (as a Service) Managed by vendor Storage Servers Networking O/S Middleware Virtualization Applications Runtime Data

Software as a Service (SaaS) Complete apps you use Subscribe, on-board, normally pay for the # of users who use the app No access to underlying platform Software may support some customizations Shared hardware, platform and finished software across multiple customers Build ON PaaS services Finished Applications (you supply the data) (CRM, ERP, Exchange, SharePoint, etc.) ComputeStorageWebDatabase VM

A Platform for ISV’s The Foundation for Private Cloud

Compute $ /hour + Variable Instance Sizes Per service hour Storage Per GB stored and transactions $0.15 GB/month $0.01/10k transactions Caching 128MB cache for $45/month Per Message Operation $1.99/10k transactions Per Message Operation Access Control $0.10/100 Relay Hours $0.01/10,000 Messages (Queues/Topics/Relays) Per Message Operation Service Bus Web Edition $9.99/month (up to 1 GB DB/month ) Per database/month Business Edition Per database/month Starting at $99.99/month (10-50 GB DB/month )

Small (moderate IO) 1.75 GB memory 250 GB storage (instance storage) Medium (high IO) 3.5 GB memory 500 GB storage (instance storage) Small Medium X-Large Large (high IO) 7.0 GB memory 1000 GB storage (instance storage) X-Large (high IO) 14 GB memory 2000 GB (instance storage) Extra Small (low IO) 768 MB memory 20 GB storage (instance storage)

26