Windows Azure Cloud Services

1. Windows AzureCloud Services Anton Boyko .NET developer

2. Agenda A brief overview of Windows Azure Compute Services and application scenarios Windows Azure Cloud Services basics Windows Azure Cloud Service lifecycle Windows Azure Cloud Services communication capabilities

3. Azure Compute

4. Azure compute Control Flexibility Management Complexity Cloud Services Web Sites Virtual Machines

5. Windows Azure • Your Datacenter • Virtual Machines • Cloud Services • Web Sites Applications Applications Applications Applications Data Data Data Data Firewall Firewall Rules Firewall Rules Network Virtual Network Virtual Network O/S O/S Virtualization Hardware Focus on the Application

6. Application Scenarios Web Sites Cloud Services Virtual Machines Modern web apps Perfect if your app consists of client side markup and scripting, server side scripting and a database. Powerful capability to scale out and up as needed. Multi-tier applications Cloud-based applications that separate application logic into multiple tiers (i.e. caching middle tier, asynchronous background processes like order processing) using both Web and Worker Roles Enterprise server applications Run your existing enterprise applications in the cloud, such as SQL Server, SharePoint Server or Active Directory. Continuous development Deploy directly from your source code repository, using Git or Team Foundation Service. Apps that require advanced administration Cloud-based applications that require admin access, remote desktop access or elevated permissions Porting existing line of business apps Choose an image from the library or upload your own VHD. Popular open source apps Launch a professional looking site with a few clicks using apps like WordPress, Joomla!, Drupal, DotNetNuke and Umbraco Apps that require advanced networking Cloud-based applications that require network isolation for use with Windows Azure Connect or Windows Azure Virtual Network Windows or Linux operating system Support for Windows Server, along with community and commercial versions of Linux. Connect virtual machines with cloud services to take full advantage of PaaS services.

7. Cloud Service Overview

8. What is a Cloud Service? A collection of related service roles Web Role Worker Role

9. What Can It Run? • General Rule • If it runs in Windows it can run as a Cloud Service • Choice of Language • C#, VB, C++, Java, PHP, Node.js, Phython, etc. • Choice of Frameworks • .NET, ExpressJS, Rails, Zend, etc.

10. Web Role and Worker Role Windows Server (+ IIS 7, 7.5 or IIS 8.0* for Web Role) ASP.NET 3.5 SP1, 4.0 or 4.5* – 64bit Hosts Webforms or MVC FastCGI applications (e.g. PHP) Http(s) Web/Worker Hybrid Can optionally implement RoleEntryPoint *for Windows Server 2012

11. Worker Role Patterns Queue Polling Worker Push and Pop Messages within while(true) loop E.g. Map/Reduce pattern, background image processing Listening Worker Role Create TcpListener or WCF Service Host E.g. Run a .NET SMTP server or WCF Service External Process Worker Role OnStart or Run method executes Process.Start() Startup Task installs or executes background/foreground process Custom Role Entry Point (executable or .Net assembly) E.g. Run a database server, web server, distributed cache

12. Roles and Instances • Roles are defined in a Hosted Service • A role definition specifies: • Virtual machine size • Communication endpoints • Local storage resources • etc. • At runtime each Role will execute on one or more instances • A role instance is a set of code, configuration, and local data, deployed in a dedicated VM

13. Roles and Instances • Deployment (anton.cloudapp.net) • Hosted Service • Environment • Production • Staging • Role • Web Role 1 • Web Role 2 • Worker Role 1 • Instance • Web 1 Instance 0 • Web 1 Instance 1 • Web 1 Instance 2 • Web 2 Instance 0 • Worker 1 Instance 0 • Worker 1 Instance 1 6 × VM

14. Cloud Service Availability

15. Fault Domains 99.95% Uptime Guarantee Requires 2 or more instance per role Role instance are isolated by fault domain Fault domains isolate VMs Fault domains provide redundancy At least two fault domains per role

16. Roles and InstancesExample role with nine virtual machines distributed across three fault domains Network Load Balancer Role Fault Domain 1 Fault Domain 2 Fault Domain 3 VM1 VM3 VM2 VM4 VM6 VM9 VM5 VM8 VM6 VM9

17. Fault and Update Domains Fault Domain Fault Domain Rack Rack Web Role UD #1 UD #2 INSTANCE INSTANCE INSTANCE INSTANCE Worker Role UD #1 UD #2 INSTANCE INSTANCE INSTANCE INSTANCE

18. Cloud Service Lifecycle

19. Understanding Packaging and Config Windows Azure Services are described by two artifacts: Service Definition (*.csdef) Service Configuration (*.cscfg) Your code is zipped and packaged with definition (*.cspkg) Encrypted(Zipped(Code + *.csdef)) == *.cspkg Windows Azure consumes just (*.cspkg + *.cscfg)

20. Role Lifecycle All roles may extend RoleEntryPoint Roles report status via RoleEnvironment Methods Events Status OnStart StatusCheck Busy Fabric Calls Requests Routed Run Ready StatusCheck Role Lifetime OnStop StatusCheck Busy Stopping

21. Packaging & Deployment ServiceCode *.cspkg Windows Azure Compute Controller Service Model Config *.cscfg Upload to Windows Azure LB Service Microsoft Visual Studio You can also integrate with source control such as TFS and deploy via continuous integration. Visual Studio Tools for Windows Azure supports one-click deployment. Aimed at rapid build/deploy/test/fix scenarios. Service Web Role Worker Role

22. Cloud ServiceCommunication

23. Cloud Service – inter-role communication • Internal Endpoint • Not load-balanced • HTTP/TCP/UDP/ANY • Input Endpoint • Load-balanced • HTTP/HTTPS/TCP/UDP • Other options • Queue • Storage • Database • … • Instance Input Endpoint • Route traffic to specific instance based on port • TCP/UPD

24. Azure Cloud Services Demo