Overall Satisfaction with Azure App Service
Azure App is being used to host our .NET applications. Runtime stack for these are .NET 2.1. Azure has good support for .NET applications. So we prefer using Azure for .NET.
It is integrated will with Azure DevOps. So we use piplelines to deploy code.
It is integrated will with Azure DevOps. So we use piplelines to deploy code.
- It has options to deploy using CI/CD.
- It has great integration with Azure Devops
- It has all the common runtimes, so we don't need to install softwares.
- Some times our .NET API Service crashes and it is hard to find the root cause.
- Quick Links to frequently used pages will help
- PHP 8 is not supported yet.
- Devops CI/CD piplelines
- Azure Kubernetes
- We use the Sprint Board for project Planning.
- Download time is reduced because of auto scaling feature.
- Insight tool helps in finding issues quickly.
- CI/CD has helped in automation.
- We selected Azure over Linode because of the CI/CD integration with DevOps.
- Azure has integration with docker containers.
- Azure has intehration with Sprint Planning.
- If cost budget less than Linode is cheaper.
- Azure has auto scaling feature which is not there in Lonode.
- All of the server settings and deployment in Azure can be done from the UI. In Linode you will need some knowledge of cli commands.
Do you think Azure App Service delivers good value for the price?
Yes
Are you happy with Azure App Service's feature set?
Yes
Did Azure App Service live up to sales and marketing promises?
Yes
Did implementation of Azure App Service go as expected?
Yes
Would you buy Azure App Service again?
Yes