Design web apps Flashcards
(29 cards)
Overview
1) Globally scale websites
2) Create websites using Microsoft Visual Studio
3) Debug websites
4) Understand supported languages
5) Websites, VMs, and cloud services
CDN setup
1) Endpoint
2) Protocol enabled
3) Query string status
4) domain names
Azure Traffic Manager
1) use a single URL to reference all of them
2) closest possible geographically
3) provides better control on where the other web applications are being deployed around the world
CDN Vs Azure Traffic Manager
CDN will deploy when it is called from a location, whereas by using a Traffic Manager, the locations are all planned out carefully at the beginning.
Monitor
1) Monitor component that is built into the blade for the web application
2) view data such as requests and errors that have occurred on the server. You also can add alerts to notify you when certain conditions are met (for example, Http Server Errors > 0)
Azure Application Insights
1) any website can send telemetry data to the Preview Management portal
2) Application Insights blade displays various captured data elements.
3) can use this to add a monitor from any webserver, not just Azure
Site Control Manager
1) can use to debug your website
2) The Site Control Manager site runs Project Kudu, which is an open-source project for managing deployments, WebJobs, and other features for Web Apps
Site Control Manager shows
currently running processes, system information, application settings, connection strings, environment variables, PATH, HTTP headers, and server variables
Deploy websites overview
1) Implement Azure Site Extensions
2) Create packages
3) Service plans
4) Deployment slots
5) Resource groups
6) Publishing options
7) Web Deploy, and FTP locations and settings
8) Settings
Implement Azure Site Extensions
1) can create and deploy custom administrator functionality.
2) can add Site Extensions to your own site and also publish it to http://www.siteextensions.net/.
Site extensions extra steps
1) add an applicationHost.xdt file
2) Add a build.cmd file to the root of your project
3) Add the new website to the Site Control Manager website
4) Restart your website
5) https://.scm.azurewebsites.net/, where is your site.
Publishing Profile
1) Azure PowerShell, you will need the publishing profile
2) import the publishing profile file in visual studio
Local GIT in Azure
1) Azure will create a GIT repository and control your source code for you
2) Azure provides online backups of all changes and commits to the GIT repository
3) if you configure the deployment to use a local GIT repository
Design websites for business continuity
1) Scale-up and scale-out with App Service Web Apps and Azure SQL Database
2) Configure data replication patterns
3) Update websites with minimal downtime
4) Backup and restore data
5) Design for disaster recovery
6) Deploy websites to multiple regions for high availability
7) Design data tier
Elastic Scale
1) SQL Database offers a scaling feature called Elastic Scale
2) Sharding a database means to split it and partition the different parts to multiple drives.
3) You can scale databases horizontally to shard the database into multiple databases based on the data.
DB vertical scaling
1) Vertical scaling moves the database from a Standard pricing tier, for which the size of the database is limited to 250 GB, to a Premium pricing tier, which can support up to 500 GB.
2) combination of vertical and sharding is possible
Configure data replication patterns
1) CDN
2) SQL sync
3) SQL geo-replication
SQL sync
1) set a time interval at which the database synchronizes its data to one of more other databases.
2) SQL Sync is not a replacement for actual data replication, because it is not being run against the transactions
SQL geo-replication
1) Geo-replication sets up replica databases on other SQL Servers or in other data centers that can be used in a disaster recovery scenario
2) Create a readable backup, you need to use the Premium tier
Update websites with minimal downtime
1) use slots
2) run multiple instances and put the instances into Upgrade Domains.
Backup and restore data
1) create two files in the Blob container: an XML configuration file and a zip file with all of the files from the site.
2) If the database was backed up as well, the backup file for that will be in the content zip file at the root level.
Design for disaster recovery
1) backups are stored in Azure Blob storage
2) Storage account to a Geo-Redundant or Read-Access Geo-Redundant pricing tier instead of just locally redundant
3) back up Microsoft Hyper-V–based machines that are running on-premises
Deploy websites to multiple regions for high availability
1) can include only one web application from any given Azure Region
2) Traffic Manager to expose the websites via a single URL
configuration settings for the Traffic Manager
1) The default setting is Performance, which uses locations geographically closest to the request.
2) Round Robin distributes traffic evenly between all of the endpoints.
3) Failover specifies that the main website is used for all traffic and then the backups are used if the primary site goes offline
