掌握Azure Web App开发：最新开发者指南

需积分: 10 163 浏览量更新于2024-07-18 收藏 6.38MB PDF 举报

身份认证购VIP最低享 7 折!

领优惠券(最高得80元）

资源详情

资源推荐

Chapter 1

Microsoft Azure Web Apps

Azure App Service Web Apps (formerly Azure Websites) is a platform-as-a-service (PaaS) offering that

enables developers to build secure, mission-critical, and highly scalable web applications. Developers

can choose from languages such as C#, HTML5, PHP, Java, Node.js, and Python to write their code and

use familiar tools such as Visual Studio and platform-specific Azure SDKs to get started quickly.

This chapter will introduce you to essential knowledge to get started building Azure web apps. This

text will present topics with the ASP.NET developer in mind and, therefore, will use C# for code

samples and Visual Studio 2013 with the Azure SDK for .NET installed.

This book focuses exclusively on Azure Web Apps, not on essential aspects of the Microsoft Azure

platform or the Azure portal. Therefore, it is recommended that the reader have some knowledge of

the Microsoft Azure platform. An excellent resource to gain this knowledge is

which you can download for free from

http://blogs.msdn.com/b/microsoft_press/archive/2015/02/03/free-ebook-microsoft-azure-essentials-

fundamentals-of-azure.aspx.

Introduction to Azure Resource Groups

When you create any resource in Azure, you will associate that resource with a new or existing resource

group. Therefore, before creating a resource such as an Azure web app, it is important to understand

Azure Resource Groups.

An Azure Resource Group is a logical container for grouping Azure resources. As an example,

consider a typical website implementation that has a web front end with which users interact and a

database in which to store data. The web front end and the database are individual resources that

comprise the full website solution. An Azure Resource Group gives you a natural way to manage and

monitor resources that comprise a solution. Figure 1-1 is an example of what an Azure Resource Group

could look like for a web application consisting of an Azure web app, Redis Cache, SQL database,

DocumentDB, and an Azure Storage account.

FIGURE 1-1 A hypothetical representation of an Azure Resource Group.

Grouping resources this way helps simplify the implementation, deployment, management, and

monitoring of resources in the resource group. From a billing perspective, it gives you a way to view

costs for the resource group rather than for individual resources, eliminating the need to figure out

which resources are related. You can think of an Azure Resource Group as a unit of management.

The resources in a resource group can span regions if needed. For example, you may have a web

app that is deployed in two or more regions for high availability in the unlikely event that an entire

datacenter were to go down where your app is deployed. In this scenario, each web app could be part

of the same resource group.

A single resource may exist in only one resource group. But it is possible for resources from different

resource groups to be linked. These are referred to as resources in the Azure portal. An example

of this could be a SQL database that is shared between web apps in different resource groups. Assume

you have a SQL database named “sqldb1” that is a resource in a resource group named “resgrp1.”

Now, assume you have a second resource group named “resgrp2” with a web app resource that will

use “sqldb1.” In this example, “sqldb1” will appear as a linked resource in “resgrp2.”

Introduction to App Service Plans

An App Service Plan provides a way for you to define the region and pricing tier (capacity and features)

that can be shared across the app service types, which are Web Apps, Mobile Apps, Logic Apps, and

API Apps. There are five pricing tiers available for Azure App Services:

 Free The Free tier is intended for evaluation purposes; this is why it is free. Web apps in this

tier share machine resources with other web apps from other Azure subscribers. Because the

resources are shared, you have limited daily compute and network bandwidth limits.

 Shared The Shared tier also shares machine resources with other web apps, but the daily

compute and network bandwidth limits are increased. This tier is intended for low-traffic sites

and enables support for a few features, such as custom domains and the ability to scale out to

multiple shared instances.

 Basic The Basic tier gives you dedicated machine instances to host your web app and,

therefore, has no daily resource limits. In this tier, you are able to scale up the size of your

dedicated virtual machine to increase the number of cores and RAM. This tier enables

additional Azure Web App features and also is backed by a service level agreement (SLA).

 Standard The Standard tier has all the features of the Basic tier, and it enables all features

available to Azure Web Apps. Features such as autoscale, deployment slots, automated backups,

support for Microsoft Azure Traffic Manager, and more are enabled in this tier.

 Premium The Premium tier (in preview) provides the same set of features as the Standard tier

but with some extra capacity for features such as the number of deployment slots, storage, and

backups. It also enables BizTalk integration capabilities.

For details on the capacity, features, and costs associated with each pricing tier, see

http://azure.microsoft.com/en-us/pricing/details/app-service/.

An Azure web app may exist in a single App Service Plan at any given time. Or when needed, a web

app may be moved to another App Service Plan. This gives you the flexibility of starting your web app

development in an App Service Plan configured for the Free tier and then upgrading to an App Service

Plan configured for a higher pricing tier as your application and development requirements expand.

An App Service Plan can be used for multiple Web Apps, Mobile Apps, Logic Apps, and API Apps.

For example, you may have a plan that you use for development and testing your web apps that is

configured with less capacity and fewer features. Or you may have a plan that you use for a common

set of customer web apps in a specific region.

At any time, you can change the pricing tier for your App Service Plan. So it is not necessary to

create a new one if you need to move to a higher or lower pricing tier.

Important Changing the pricing tier for an App Service Plan will change the tier for all web apps in

the plan. For example, if you have five web apps running in a plan configured for the Basic tier and

later change the pricing tier to Standard, then all five web apps will be upgraded to run on Standard

Virtual Machines instead of Basic Virtual Machines.

An App Service Plan is a component of Azure Resource Groups, discussed in the previous section. At

first, this may not seem intuitive, but if you think of an Azure web app as a resource in a resource

group and an App Service Plan as a way to define the features and capacity available to your web app,

then the relationship between the two is easier to comprehend. For more information on the

relationship between Azure Resource Groups and App Service Plans, see

http://azure.microsoft.com/en-us/documentation/articles/azure-web-sites-web-hosting-plans-in-

depth-overview/.

Create an Azure Web App using the Azure portal

The Azure portal at https://portal.azure.com provides a rich user interface to provision and manage

resources in your Azure subscription. In this section, you will create an Azure web app with a SQL

database and then add an Azure Redis Cache to the resource group. After completing the steps, you

will have an Azure web app to which you can publish a web application. Publishing a web

application such as an ASP.NET MVC application is covered later in this chapter.

Create a Web App and SQL Database

After signing in to the Azure portal, click the +NEW button in the lower-left corner of the page. In the

Create blade, select the Web + Mobile option. In the Web + Mobile blade, you will see options for

creating various resources in Azure App Service, such as Web Apps, Mobile Apps, Logic Apps, and API

Apps.

Note If your goal is to create just an Azure web app, then you could select the option for Web Apps

where you would have the opportunity to specify an Azure Resource Group and App Service Plan for

the web app.

At the bottom of the Web + Mobile blade, click Azure Marketplace. In the Azure Marketplace,

additional options are available for creating common Azure Web App environments, such as a web

app with a SQL database or a web app with a MySQL database, as shown in Figure 1-2.

FIGURE 1-2 Web App solutions in the Azure Marketplace.

Tip There are many options for Web Apps you can choose from in the Azure Marketplace that

provide solutions for popular configurations such as blogging sites, frameworks, ASP.NET Starter apps,

and more. The full selection of solutions can be found in the Web Applications section of the

Marketplace at http://azure.microsoft.com/en-us/marketplace/web-applications/. To create a web app

using one of the solutions, click the solution. You will be redirected back to the Azure portal where

you can configure the solution settings for your needs.

Select the Web App + SQL option, which will open a blade describing the resources that this

solution will create and also provides links to relevant resources. Next, click the Create button at the

bottom of the blade to begin configuring the web app and SQL database.

剩余125页未读，继续阅读

IAMITPRO

粉丝: 43
资源: 7

掌握Azure Web App开发：最新开发者指南

VisualStudio2019手册.zip

LeiZhangAzureCloudService用户手册1

Azure Logic App

AZure app的bolo在哪里看

azure 操作手册

适用于Azure扩展

azure springboot

azure-kinect-unreal

azure认证中文考试

Cloud Service和App Service

azure+kinect

文本转换语音azure

Azure Kinect

azure kinect dk骨骼点坐标

azure kinect examples for unity 1.16

windows azure step by step

走进云计算 : windows azure实战手记 下载

netcore 2.2 调用 azure openai

azure文本转语音csdn

如何布置Azure AVD

最新资源

走进云计算 : windows azure实战手记下载