http://netponto.org 14ª Reunião Presencial - 18/09/2010 Windows Azure para DevelopersLuis Martins
Luis Martins Architect Evangelist na Microsoft desde 2008. Desempenhou várias funções de IT em sectores diferenciados sempre com um especial foco de atenção no aumento de produtividade e criação de valor. Está focado na arquitectura das soluções, Software + Services, Cloud Computing e qualquer solução que transforme a User Experience em divertimento.
1. types of cloud services infrastructure as a service “SaaS” “PaaS” “IaaS” platform as a service software as a service consume it migrate to it build on it Microsoft Azure Microsoft BPOS Microsoft Azure
5. cost Server Energy other Source James Hamilton: http://perspectives.mvdirona.com/2008/11/28/CostOfPowerInLargeScaleDataCenters.aspx
5. cost Server Power Energy and cool.inf other
6. optimalworkload patterns for the cloud “On and Off “ Inactivity Period Compute Usage Average Time On and off workloads (e.g. batch job) Over provisioned capacity is wasted Time to market can be cumbersome
6. optimalworkload patterns for the cloud “Growing Fast“ “On and Off “ Inactivity Period Compute Compute Average Usage Usage Average Time Time On and off workloads (e.g. batch job) Over provisioned capacity is wasted Time to market can be cumbersome Successful services needs to grow/scale Keeping up w/growth is big IT challenge Complex lead time for deployment
6. optimalworkload patterns for the cloud “Unpredictable Bursting“ Compute Average Usage Time Unexpected/unplanned peak in demand Sudden spike impacts performance Can’t over provision for extreme cases
6. optimalworkload patterns for the cloud “Unpredictable Bursting“ “Predictable Bursting“ Compute Compute Average Usage Average Usage Time Time Unexpected/unplanned peak in demand Sudden spike impacts performance Can’t over provision for extreme cases Services with micro seasonality trends Peaks due to periodic increased demand IT complexity and wasted capacity
7. platform continuum Private or Public Cloud Windows Server Traditional Datacenter Cloud Platform Windows Azure Private or Public Cloud Azure Appliance On Premises Off Premises
moving to the Clouddoes not imply anew business model
software as a service customer try/buy username+password subscription is based on time or consumption - Flat fee - Application usage
software in a box customer has an Azure subscription two options: - customer gives a certificate to the supplier to deploy the solution - supplier gives package to customer and customer deploys the package
technical new application migrating existing applications
new application get Azure SDK get ASP membership providers for Azure business as usual… …let’s have a SQL vsnoSQL talk?
existing application two options: don’t think, try! check architecture and tools look at the blockers
blockers? no best practices no best practices no best practices no best practices no best practices
blockers – generic? no SMTP server? no FTP server? missing storage tools? long try and buy
blockers – SQL? SQL clients must be updated no SQL Agent no CLR no full text search no cross database queries no reporting services 50Gb?
blockers – web role? one role => one site debugging monitoring tools