How to convince someone to use Azure Static Web app over Azure App Service

Question

We currently have a huge Blazor WASM project that runs on an App Service. I want to convince my boss that we should move this application from running on an App Service to running on Static Web app. Here is going to be some of his reason's why not to move it. 1. We already built the pipeline (we use deployment slots for dev, staging, production 2. We already know the cost of what we have using the App Service. 3) what do I gain by moving it - Is it faster to deploy to the user ? Is it cheaper to run on a static web app?

Answer 1

Azure Static Web Apps is a great option for hosting static web applications, and it has some advantages over Azure App Service. Here are some reasons why you might want to consider using Azure Static Web Apps instead of Azure App Service:

1. Faster deployment: Azure Static Web Apps provides a faster deployment experience than Azure App Service. With Azure Static Web Apps, you can deploy your application directly from your GitHub repository, and the deployment process is automated. This means that you can deploy your application more quickly and with less effort.
2. Cheaper to run: Azure Static Web Apps is generally cheaper to run than Azure App Service. This is because Azure Static Web Apps is designed specifically for hosting static web applications, which require less compute resources than dynamic web applications. This means that you can save money on hosting costs by using Azure Static Web Apps.
3. Better scalability: Azure Static Web Apps is designed to scale automatically based on demand. This means that you don't need to worry about scaling your application manually as traffic increases. With Azure Static Web Apps, your application will automatically scale to meet demand, which can help you avoid downtime and ensure that your application is always available.
4. Built-in security: Azure Static Web Apps provides built-in security features that can help you protect your application from common web application attacks. This includes features like automatic SSL certificate provisioning, role-based access control, and more.

In terms of your specific concerns, here are some responses:

1. Pipeline: Azure Static Web Apps integrates with GitHub Actions, which means that you can use your existing pipeline to deploy your application to Azure Static Web Apps. This means that you don't need to rebuild your pipeline from scratch.
2. Cost: As mentioned earlier, Azure Static Web Apps is generally cheaper to run than Azure App Service. This means that you may be able to save money on hosting costs by using Azure Static Web Apps. (This is not a price quote. You would need to open a free billing support ticket to have them provide you with a billing estimate.)
3. Benefits: By moving your application to Azure Static Web Apps, you can benefit from faster deployment, better scalability, and built-in security features. These benefits can help you improve the performance and reliability of your application.

With that being said, I have been supporting Azure Web Apps for nearly 8 years and I do not think you can go wrong with either.