20120620 moving to windows azure


Published on

From the A

Published in: Technology, Business
  • Be the first to comment

  • Be the first to like this

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide

20120620 moving to windows azure

  1. 1. Migrating to AzureLuis Alves MartinsSolution Architect | Microsoft Services WE HQluis.martins@microsoft.com
  2. 2. how to go to the cloud?
  3. 3. Packaged Infrastructure Platform Software Software (as a Service) (as a Service) (as a Service) You manage Applications Applications Applications Applications You manage Data Data Data Data Runtime Runtime Runtime Runtime Managed by vendor efficiencyMiddlewareYou manage Middleware Middleware Middleware Managed by vendor O/S maturity O/S O/S O/S Managed by vendor Virtualization Virtualization Virtualization Virtualization Servers Servers control Servers Servers Storage Storage Storage Storage Networking Networking Networking Networking
  4. 4. (on-premise) Client Layer On- On- Office Games premise premise Add-in PC Tablet Phone Browser Console Service DatabaseIntegration Layer Traffic Virtual Access CDN Manager Network Connect EAI / EDI Service Bus Control Data SyncApplication Layer Media Virtual Services Compute Web Sites Cloud Machines Hadoop ServicesData Layer Storage Drive Blobs Tables Queues Caching SQL Azure Reporting Database
  5. 5. what changes?
  6. 6. compliance ? “my app is 18!”
  7. 7. compliance “scalability = scaling out” scalability“Scalability is anarchitecture feature, elasticityelasticity is aplatform feature”– Luis Calado
  8. 8. compliancescalabilityperformance
  9. 9. compliance Infrastructure Platformscalability (as a Service) (as a Service) You manage Applications Applications You manageperformance Data Data Runtime Runtime Middleware Middleware Managed by vendorsecurity O/S O/S Managed by vendor Virtualization Virtualization Servers Servers Storage Storage Networking Networking
  10. 10. compliance Infrastructure Platformscalability (as a Service) (as a Service) You manage Applications Applications You manageperformance Data Data Runtime Runtime Middleware Middleware Managed by vendorsecurity O/S O/S Managed by vendor Virtualization Virtualization Servers Serversoperations Storage Networking Storage Networking
  11. 11. The 5 R’s http://www.gartner.com/id=1485116
  12. 12. IaaSBatch at Scale
  13. 13. Using the CDNUsing Table StorageStoring PCI data in a Partner cloud
  14. 14. moved to partner cloudwith new development to extend itin public cloud
  15. 15. Java to C#
  16. 16. new SaaS solution
  17. 17. Time Internal Cost Integration Your Choice?REHOST Change the hostREFACTOR Change it Fill according Take advantage to yourREVISE of the cloud company, culture,REBUILD Do it again priorities and moneyREPLACE Buy new solution
  18. 18. Low High
  19. 19. no application No man is an island, “No man is an island”is an island Entire of itself. Each is a piece of the continent, A part of the main. If a clod be washed away by the sea, Europe is the less. As well as if a promontory were. As well as if a manor of thine own Or of thine friends were. Each mans death diminishes me, For I am involved in mankind. Therefore, send not to know For whom the bell tolls, John Donne It tolls for thee. (1572-1631)
  20. 20. Bring entire application Bring portion ofand all dependencies application to the cloud while some resources stay on-premises
  21. 21. scenario to avoid(most of the times) Latency? Security? “Chattiness”?
  22. 22. safer solutionOne-way sync to cloud Disaster RecoveryOne-way sync from cloud Consolidation scenarios Using the cloud forTwo-way sync internet and mobile availability
  23. 23. Windows Azure Virtual Network
  24. 24. Hybrid Public/Private CloudEnterprise app in Windows Azure requiring connectivity to on-premiseresourcesManage identity and access control with on-premise resources(on-premises Active Directory)Remote monitoring and trouble-shooting of resourcesrunning in Windows AzureCloud deployments requiring persistent IP addressesand direct connectivity across services
  25. 25. common scenarios
  26. 26. Branch A Branch B Multiple office/branch locations Share data between locations Aggregate data in the cloud
  27. 27. Branch A Geographic located applications - Use with Azure Traffic Manager Disaster Recovery
  28. 28. Scaling out the applicationSeparating workloads, Reporting, Analytics
  29. 29. migrating...
  30. 30. Connect Cloud Apps via VIPs• Easily compose services by connecting public endpoints• For advanced connectivity scenarios such as Active Directory or DCOM• Simple, secure and highly efficient method of using IaaS and PaaS side-by-side
  31. 31. • Do not use write caching• Avoid using OS drive for large databases• Consider putting database and transaction log files on separate drives• Consider putting tempdb on the non-persistent cache disk (D:)• Consider using database page compression to reduce I/O• Consider latency between primary and replica when choosing sync mode
  32. 32. http://blogs.msdn.com/b/sqlazure/archive/2010/08/04/10046103.aspx http://code.msdn.microsoft.com/Windows-Azure-ASPNET-03d5dc14
  33. 33. • See “Windows Azure Accelerator for Web Roles”
  34. 34. http://sqlazuremw.codeplex.com/
  35. 35. • Size (actual max:150Gb) – SQL Azure Federations• All tables require clustered indexes – solution: refactor• No Full-T Search ext – Use FAST or Lucene.net or do-it yourself• No Cross Database Joins available (or Linked Servers) – Use schemas, refactor• No SQL-CLR – Refactor, please• Performance SQL Azure info: http://msdn.microsoft.com/en-us/library/ee336279.aspx
  36. 36. Tables, indexes and views Change Data Capture Cross Database JoinsStored Procedures Data AuditingFunctions Data CompressionCursors Database file placement Database mirroringTriggers External Key Management / Extensible Key ManagementConstraints FILESTREAM DataTable variables, session temp tables (#t) Full-text Search / IndexesSpatial types Global temporary tables Performance Data Collection (Data Collector)HierarchyId Policy-Based ManagementSparse Columns Resource GovernorThrow statement SQL-CLR SQL Server Replication Transparent Data Encryption Table Partitions
  37. 37. • Logs• Static Data• Cached tables• Performance counters• Azure storage analytics
  38. 38. Cloud Ready(Paas)
  39. 39. Azure On premises Both ServiceConfiguration web.config Check if running in AzureConfiguration .csdef and .cscfg app.config and use accordingly Blob: File handling class Blob: File Storage Table: Interface to SQL ServerStorage Azure Storage Table: SQL Server SAL? Queues: Abstraction layer (always with a configuration Queues: MSMQ switch) Memory, SQL Azure, Memory, SQL Server, Configure at web.configSession Azure Storage, Cache Cache level Use the commonDatabase SQL Azure SQL Server subset of functionality. Isolate other features
  40. 40. wrap up
  41. 41. Many Applications could benefit from migrating to a mixed deployment.Migrating to web/worker roles or taking advantage of otherWindows Azure services (storage, cache etc..)Simplified Deployment and ConfigurationHealth ModelEasy High AvailabilityInstance ScalabilityOS PatchingAutomatic Firewall ConfigurationSimple Certificate DeploymentMany others
  42. 42. Use Virtual Machines and VNET for Forklift Migration
  43. 43. Q&A(more)
  44. 44. thankLuis Alves Martins luis.martins@microsoft.com