Cloud Transformation

Mission-Critical Web App on App Service

Web app and API on App Service in two regions, behind Front Door, data private and geo-replicated.

Front Door with a WAF policy is the one way in and sends users to the active region. Each region runs the web front end and API on zone-redundant App Service; data sits behind private endpoints, and Azure SQL geo-replicates to the standby region.

HTTPSfailoverprivate endpointsgeo-replicationMicrosoft AzureGlobal · edge and shared servicesRegion 1 · activeConfigurationVirtual network · private endpointsRegion 2 · warm standbyVirtual network · private endpointsUsersbrowsers, phonesWeb ApplicationFirewallAzure Front DoorPremium, globalMicrosoft Entra IDuser and staff sign-inApplication Insightsper regionAzure Monitoralerts, dashboardsAzure Policyboth regionsApp Configurationsettings, feature flagsAzure Key Vaultsecrets, certificatesWeb front endAzure App ServiceWeb APIAzure App ServicePrivate DNS zonesprivatelink namesAzure Blob Storagefiles, static contentAzure Managed Redissessions, hot readsAzure SQL Databaseprimary, zone-redundantWeb front endwarm standbyWeb APIwarm standbyAzure SQL Databasegeo-secondaryAzure Managed Redisown cache

Point at a component to light its links; select it for what it does here and the practice that makes it right on Azure.

When to use it

  • Customer-facing web apps where an outage costs money or trust
  • Users in several geographies who need one address and low latency
  • Teams that want PaaS, not clusters, for a web front end and API

How NGT delivers it

Built from code, reviewed at a gate by an NGT architect, and handed over with runbooks your team can run.

Cloud Transformation