6 | (Demo) How to create WebApp ? How to use Azure Web app as platform as service CI/CD Pipeline.
#Azure #cloud
Complete Tutorial with Demo
How to create WebApp ?
How to use Azure Web app as platform as service
CI/CD Pipeline.
How to automate deployment to azure web apps.[Build, deploy and manage powerful web apps.]
#Azure
Azure App Service is a fully managed web hosting service for building web apps, mobile
back ends and RESTful APIs.
No Need to maintain Underlying Infrastructure
Auto scaling and security
Dev-Ops capability and continuous integration
App Service Plan-
https://azure.microsoft.com/en-in/pri...
For 1 service plan underlying OS and App Framework (.NET, Java, node) should be same
When Create Azure Web Apps instance it creates 2 recourses- Azure web Apps and Azure web Apps Plan
Continuous Deployment
We can map custom domain to Azure apps
_______________________________________________________________
Scale-up – A scale up operation is the Azure Web Sites cloud equivalent of moving your non-cloud web site to a bigger physical server.
So, scale up operations are useful to consider when your site is hitting a quota, signaling that you are outgrowing your existing mode or
options. In addition, scaling up can be done on virtually any site without worrying about the implications of multi-instances data
consistency. Two examples of scale up operations in Windows Azure Web Sites are:
Scale-out – A scale out operation is the equivalent of creating multiple copies of your web site and adding a load balancer to distribute
the demand between them. When you scale out a web site in Windows Azure Web Sites there is no need to configure load balancing
separately since this is already provided by the platform.
Auto Scale-out
Auto Scaling is possible only for apps that are hosted in Standard and Premium App Service Plans.
We can configure the Auto Scale based on the following parameters.
CPU Percentage
Memory (RAM) percentage
Disk queue Length
HTTP Queue Length
Data in
Data Out
WebJobs is a feature of Azure App Service that enables you to run a program or script in the same instance as a web app, API app, or mobile app. .
Visual Studio adds the following items to a WebJobs-enabled project:
The Microsoft.Web.WebJobs.Publish NuGet package.
A webjob-publish-settings.json file that contains deployment and scheduler settings.
Scale-up – A scale up operation is the Azure Web Sites cloud equivalent of moving your non-cloud web site to a bigger physical server. So, scale up
operations are useful to consider when your site is hitting a quota, signaling that you are outgrowing your existing mode or options. In addition, scaling
up can be done on virtually any site without worrying about the implications of multi-instances data consistency. Two examples of scale up operations in
Windows Azure Web Sites are:
Scale-out – A scale out operation is the equivalent of creating multiple copies of your web site and adding a load balancer to distribute the demand
between them. When you scale out a web site in Windows Azure Web Sites there is no need to configure load balancing separately since this is already
provided by the platform.
Auto Scale-out
Auto Scaling is possible only for apps that are hosted in Standard and Premium App Service Plans.
We can configure the Auto Scale based on the following parameters.
CPU Percentage
Memory (RAM) percentage
Disk queue Length
HTTP Queue Length
Azure App Configuration allows developers to store, retrieve and manage access to application settings all in
one place. It is easy to set up and simple to use from any application. It gives developers the ability to modify an
application's behavior on demand without having to redeploy the application. App Configuration offers the
following benefits:
A fully managed service that can be set up in minutes.
Flexible key representations and mappings.
Versioning with labels.
Point-in-time replay of settings.
Comparison of two sets of configurations on custom-defined dimensions.
Enhanced security through Azure-managed identities.
Complete data encryption, at rest or in transit.
Native integration with popular frameworks, including .NET and Java.
--------------------
Deployment slots allow your function app to run different instances called "slots". Slots are different environments
exposed via a publicly available endpoint. . If a app is running during a swap, execution continues and the next triggers
are routed to the swapped app instance.
Benefits of deployment slots include: You can validate web app changes in a staging deployment slot before swapping it
with the production slot. Deploying a web app to a slot first and swapping it into production ensures that all instances of
the slot are warmed up before being swapped into production.
Azure Web Sites has increased the number of deployment slots for Standard websites to 4 (in addition to the
Production slot). This gives you more deployment options, since you can keep multiple versions of your site and alternate
between them while continuing to develop.