CHAPTER2 UNDERSTANDING WINDOWSAZURE PLATFORMARCHITECTURE

Size: px

Start display at page:

Download "CHAPTER2 UNDERSTANDING WINDOWSAZURE PLATFORMARCHITECTURE"

Brook Page
5 years ago
Views:

1 CHAPTER2 UNDERSTANDING WINDOWSAZURE PLATFORMARCHITECTURE

2 CONTENTS The Windows Azure Developer Portal Creating and running Projects in the Azure Development Platform Using Azure Application Templates for Visual Studio 2008 Taking advantage of Auxiliary Cloud Services Deploying Application and Services to the Azure Cloud. 2

3 INTRODUCTION The Windows Azure Platform is Microsoft s Windows Platforms a Service (PaaS) offering that runs on servers and related network infrastructure located in Microsoft data centers and is connected to the public Internet. The platform consists of a highly scalable (elastic) cloud operating system, data storage fabric and related services delivered by physical or logical (virtualized) Windows Server 2008 instances. The Windows Azure Software Development Kit (SDK) provides a development version of the cloud-based services, as well as the tools and APIs needed to develop, deploy, and manage scalable services in Windows Azure, including Visual Studio 2008 or 2010 templates for a standardized set of Azure applications

4 INTRODUCTION According to Microsoft, the primary uses for Azure are to Add web service capabilities to existing packaged applications Build, modify, and distribute applications to the Web with minimal on-premises resources Perform services, such as large-volume storage, batch processing, intense or high-volume computations, and so on, off premises Create, test, debug, and distribute web services quickly and inexpensively Reduce costs and risks of building and extending on-premises resources Reduce the effort and costs of IT management Microsoft promises support for executing Ruby, PHP, and Python code in the cloud platform

5 SDK. 5

6 THE WINDOWS AZURE DEVELOPER PORTAL The initial entry point for Azure developers moving ASP.NET applications to the cloud is the Windows Azure Development Portal which requires logging in with a Windows Live ID. Azure Community Technical Previews (CTPs) require separate GUID tokens for Windows Azure, which includes Azure Hosted Services Storage Accounts SQL Azure Live Services P/ 6

7 7

8 CREATING AND RUNNING PROJECTS IN THE AZURE DEVELOPMENT PLATFORM Azure Cloud Fabric and Azure Storage Services don t support cloud-based development or debugging operations, so the Azure SDK provides on-premises clones in the form of the Development Fabric (DF) and Development Storage (DS) applications, which the Windows Azure SDK installs. 8

9 REQUIREMENTS.NET Framework 3.5 SP1 and SQL Express 2005 or 2008 must be present. you must enable ASP.NET and WCF HTTP Activation for IIS 7.0 under Windows Server 2008, Windows Vista SP2,or Windows 7 RC or later to install and run the SDK. 9

10 INSTALLING WINDOWS AZURE SDK AND TOOLS 1)Install Azure SDKs FOR VISUAL STUDIO The Download link is as follows 2) Download and install the Windows Azure Tools for Visual Studio to add templates for Web Cloud Service, Worker Cloud Service and Workflow Service projects. 3) Windows PowerShell is required to run the CloudDrive sample. 10

11 INSTALLING AND BUILDING THE WINDOWS AZURE SDK SAMPLE APPLICATIONS Installing the Windows Azure SDK doesn t install its sample applications, which are included in the C:\Program Files\Microsoft Windows Azure SDK\v1.0\samples.zip file. Install the sample files by unzipping samples.zip to a folder to which you have write access. C:\Windows Azure SDK Samples folder 11

$exe, DFMonitor.exe, and DFService.exe, which the Azure SDK setup program installs by default in the development PC s \Program Files\Windows Azure SDK\v1.$

12 THE DEVELOPMENT FABRIC Simulates the Windows Azure fabric so that you can run and test a service locally before deploying it. DF comprises the following executables: DFAgent.exe, DFLoadBalancer.exe, DFMonitor.exe, and DFService.exe, which the Azure SDK setup program installs by default in the development PC s \Program Files\Windows Azure SDK\v1.0\bin\devfabric folder To start DFRight-click the DF icon in the Taskbar s Notification Area, if present, and choose Start Development Fabric Service 12

13 THE DEVELOPMENT FABRIC Compile and run an Azure-enabled application in Visual Studio 13

DEVELOPMENT STORAGE The Windows Azure Platform supports three types of scalable persistent storage unstructured data (blobs) structured data (tables) messages between applications, services, or both

14 DEVELOPMENT STORAGE The Windows Azure Platform supports three types of scalable persistent storage unstructured data (blobs) structured data (tables) messages between applications, services, or both (queues) Executing rundevstore.exe or building and running Azure user code in Visual Studio starts all three services, even if your project requires only one, and displays the Development Storage 14

15 DEVELOPMENT STORAGE To protect against data loss, the Azure cloud stores blobs, tables, and queues in at least three separate containers in a single data center. Azure s geolocation features let you duplicate data in multiple Microsoft data centers for enhanced disaster recovery and to improve performance in specific geographic regions. 15

16 AZURE SERVICE DEFINITION AND SERVICE CONFIGURATION FILES Azure applications that you run in the Development Framework can access data stored locally in Development Storage or uploaded to Azure cloud storage The application looks for the port number and stored data in the location specified as endpoints in the project s Service Configuration.cscfg file. An Azure project s ServiceDefinition.csdef file defines a set of standard input endpoints and configuration settings whose values the ServiceConfiguration.cscfg file stores. 16

17 17

18 18

19 19

20 AZURE TABLE SERVICES Choosing Tools, Table Service Properties in the DevelopmentStorage.exe application opens a dialog of the same name to let you change the SQL Server Express Edition database name that stores development schemas. Azure Blob Services Blobs store binary data, such as images, XML documents, compressed (zipped or gzipped) files, and other content as an arbitrary array of bytes within a container that s associated with a storage account. A container is a user-defined set of blobs that has only properties, which include a list of the blobs it contains. Containers don t store data directly. 20

21 21

22 AZURE QUEUE SERVICES Azure queues are messages up to 8KB in size that any client or application with access to the storage account can access on a first-in, first-out basis. Azure queues have a REST API that s similar to that for blobs 22

23 USING AZURE APPLICATION TEMPLATES FOR VISUAL STUDIO 2008 Downloading Windows Azure Tools for Visual Studio adds a Cloud Service template node to the New Project dialog. Double-clicking the Cloud Service node opens the New Cloud Service Project dialog, which enables adding ASP.NET Web Roles, Worker Roles or CGI Web Roles to the project. Projects that use the Web Role template provide an ASP.NET Default.aspx web page as the starting point for a default cloud application UI 23

24 24

25 USING AZURE APPLICATION TEMPLATES FOR VISUAL STUDIO 2008 The Live Framework node appears in the New Project dialog s Project Types pane only if you install Windows Azure Tools for Visual Studio, Live Framework SDK, and Live Framework Tools. 25

26 TAKING ADVANTAGE OF AUXILIARY CLOUD SERVICES The Windows Azure Platform incorporates three sets of auxiliary services.net Services, SQL Azure Database, and Live Services. 26

27 .NET SERVICES Microsoft.NET Services are a set of scalable, developeroriented services that are hosted by Windows Azure alongside Azure Storage Services in Microsoft data centers..net Services provide key infrastructure components for cloud-based Web and Worker applications.net provides Access Control, Service Bus, and Workflow services to take advantage of Web-standard protocols. 27

28 ACCESS CONTROL SERVICES Microsoft claims that Access Control Services (ACS) provide an easy way to control web applications and services while integrating with standards-based identity providers, including enterprise directories and web identity systems such as Windows Live ID. The advantage of ACS is that you can write a set of declarative rules that can transform incoming security claims into a claims-based, federated identity to minimize developer effort. ACS relies on well-known user account stores, such as Live ID, Active Directory, or other stores that support Atom, Atom Pub, SOAP or WS-*, and HTTP protocols. 28

29 SERVICE BUS Microsoft states that the.net Service Bus (SB), makes it easy to connect applications together over the Internet Services that register on the Bus can easily be discovered and accessed, across any network topology. SB implements that Enterprise Service Bus (ESB) application pattern with Windows Communication Foundation (WCF). 29

30 WORKFLOW SERVICES Microsoft describes the.net Workflow Services (WFS) as a high-scale host for running workflows in the cloud. WFS orchestrates the sending, receiving, and manipulating of HTTP and Service Bus messages. It also provides hosted tools to deploy, manage, and track the execution of workflow instances, as well as a group of management APIs. 30

31 SQL AZURE SQL Services are highly scalable, on-demand relational database management, business intelligence (BI), and reporting utility services based provided by SQL Server 2008 SQL Data Services and SQL Azure Database (SADB) SQL Azure Database (SADB) was originally called SQL Server Data Services (SSDS) when Microsoft announced SSDS as a standalone Database as a Service (DaaS) SSDS s initial architecture implemented schema less EAV tables similar to Azure s Table Services in a non-relational 31 Authority, Container, Entity (ACE) model.

32 SADB WILL OFFER THE FOLLOWING SQL SERVER FEATURES: Tables, indexes, and views Stored procedures and triggers Constraints Table variables Session temporary tables (#t) 32

33 DEPLOYING APPLICATION S AND SER VICES TO THE AZURE CLOUD Azure Storage Services Changing from Development to Azure cloud storage requires only modifying the ServiceConfiguration.cscfg to change the AccountName value to the cloud storage project name and change the BlogStorageEndpoint, QueueStorageEndpoint, TableStorageEndpoing or all three values to

34 PUBLISHING PROJECTS TO THE AZURE SERVICES DEVELOPER PORTAL When you create a new hosting project in the online Windows Azure Development Portal, Windows Azure assigns it a GUID as a Private Deployment ID. You could synchronize your Visual Studio development project with the live version by opening the Properties window for the master project node and selecting the Portal Provisioning page to expose the Application ID text box. You could copy the ID value from the portal page and paste it to the Portal properties page s text box, 34

35 35

36 PUBLISHING THE PROJECT TO THE CLOUD FABRIC Publishing the project requires copying a package (ProjectName.cspkg) and a configuration file (*ServiceConfiguration.cscfg) to your Windows Azure instance. A package for the cloud consists of a zipped and encrypted version of the development package file (*.csx) created when you run the project in the Development Fabric. With the Application ID pasted into the Portal properties page, right-clicking the master project node and choosing Publish opens an Explorer window for the project s 36

37 37

38 38

39 THANK YOU 39

40 40

Developing Microsoft Azure Solutions

Course 20532C: Developing Microsoft Azure Solutions Course details Course Outline Module 1: OVERVIEW OF THE MICROSOFT AZURE PLATFORM This module reviews the services available in the Azure platform and