Azure App Service is a fully managed Platform as a Service (PaaS) that integrates bunch of services into a single service. One of its valuable service is Azure Web Apps that helps to develop and deploy enterprise-ready web applications. Microsoft Azure will take care of application deployment and management, while the developer only needs to concentrate on app development.
It is not unsual that we run into problems related to the deployment and post-installation. But Azure team is aware of these issues and continuously keeps improving the Azure stack.
The solution is very stable.
Microsoft provides a lot of scalability in all their services. Microsoft provides services and infrastructure, but for full scalability, the maker should take into consideration the scalability of the app home. The full scalability Microsoft provides is a way to scale up and scale up in your environment. But it doesn't take responsibility to make your web application scalable or not. It helps you to scale up, but it doesn't take care of your application's scalability.
Technical support from Microsoft is very good at all levels.
The initial setup is not too simple but not too complex. The interface makes it easy to use if you have known it for a while. For me, it's easy because I've already gotten used to it. But it could be, complex if you haven't.
The initial setup level of difficulty is dependent on what you want exactly. To set up a website on the app service, for example, is very easy for a simple website because all you need is to develop your website, build it with the Visual Studio, and configure. Once you want to deploy to app service, once you finish, it's only one button you click and everything will be deployed. It's very easy.
Deployment depends on how big your website is, so I cannot say exactly how long it will take in every case, but it is quite fast. It depends what are you sending, how many megabytes you're sending to the app service, but the app service is very fast. If you have a small website, just a few megabytes, 2, 3, 4, megabytes, you will see that it is very fast, but if you have a website with a lot of updates that takes probably five minutes, or ten minutes. That's because you need to push data to push the files to app service. The thing that I can tell you about the in-app service is that because the in-app service normally uses clocks, that means you have a development environment, staging and production environment, the customer can push more into the development environment or staging and then swap. And to swap is quite fast as well. That's the only bottleneck that is possible but Microsoft guarantees no downtime.
Most of the time we configure the ICG configuration and we put the effort in at the beginning to set up the pipeline and want to set it up so that it works automatically, so if you want to start a push code or anything will be deployed automatically. That way, fewer people are required down the road.
The benefits and costs of the Azure App Service plan varies between different tiers of web apps. It is free if you choose the Free and Shared plans app service. These plans are good only for development and testing purposes. So, before you start setting up your app service plans with multiple apps, make sure you are aware of how your chosen plan implements this.
Azure App Service is too easy to setup and appropriate for developers with no knowledge in infrastructure.
I would rate this solution an eight out of 10.
