Azure App Service design considerations part 3


This post is part of a series of Stefanos Cloud blog posts covering Azure App Service design considerations.

Part 1:

In this first part of Azure App Service design considerations ( we cover all the initial design considerations for Azure App Service PaaS.

Part 2:

Check the second blog post (Azure App Service Design Considerations Part 2) for additional design considerations which supplement the first part.

Also refer to the following freely downloadable .pdf document which includes a series of tasks and tools to plan for when designing an application migration to the Azure App Service PaaS offering:

Azure App Service design considerations part 3

In this third, and last, part of the Azure App Service design considerations post we cover items which must taken into account from an application developer perspective, when utilizing Azure App Service for migrating their apps or when designing their apps from scratch to be hosted in Azure App Service as Cloud Native apps. From a project management perspective, there are generally two general options when embarking on a Cloud project with Azure app service:

  1. You already have an application which is functional and you need to run a PoC on Azure or other public cloud with an application hosting service such as the Azure App Service. After a successful PoC you either convert the Azure PoC subscription to a production one or you create a new subscription and you either migrate all your existing resources there or you re-deploy your resources to thew new subscription.
  2. You don't have a fully functional application yet, in which case you need to migrate your code or containers to Azure App Service in a dev/test subscription, further develop and test your applications and then move to production after sufficient testing.

For a detailed explanation of cloud migration options for software applications, refer to the following article:

As a developer, you need to be aware of the following Azure App Service design considerations while you develop, test and deploy your application in the Azure Cloud. These are primarily based on the Microsoft Azure Well Architected Framework (WAF), which in turn is based on lessons learnt from the field and on a series of Microsoft best practices.

Remember that implementing Azure Well-Architected Framework (WAF) involves the following procedure (covering the assess, integrate, triage, implement, monitor phases in a continuous feedback loop).

Guidance Overview

Besides the Azure WAF App Service design considerations and best practices there are further considerations you need to make as a developer while implementing your application on Azure. Some hand-picked examples of the most important considerations are the following.