Azure App Service vs. Google Cloud Run

Azure App Service is well suited in our case :

• Our website is developed by our tech partner in a full Microsoft Azure cloud based environment.
• We gave them specific access rights and the CI / CD integration helped a lot for updates and improvements deployment.
• Most of the infra issues we had with our website weren't coming from App Service

Incentivized

Microservices and RestFul API application as it is fast and reliant. Seamless integration with event triggers such as pubsub or event arc, so you can easily integrate that with usecases with file uploads, database changes, etc. Basically great with short-lived tasks, if however, you have long-running processses, Cloud Run might not be idle for this. For example if you have a long running data processing task, other solutions such as kubeflow pipelines or dataflow are more suited for this kind of tasks. Cloud Run is also stateless, so if you need memory, you will have to connect an external database.

Incentivized

• Super quick & easy to deploy new apps in visual studio
• Easy scaling to help reduce costs during off-hours
• The powerful Azure ecosystem offers a lot of functionality that ties in well with Azure App Service

Incentivized

• Real-time autoscaling. Escalamento automático em tempo real
• Simplified Continuous Deployment. Implantação contínua simplificada
• Running tasks in the background. Execução de tarefas em segundo plano

Incentivized

• Abstraction of computing resources like Heroku does with dynos.
• Azure Portal overall is pretty bloated and that affects managing Azure App Service applications.

Incentivized

• Cloud Run doesn't allow you to redeploy an already existing revision which can be inconvenient in some use cases
• Tricky to get the deployment working to start but once it's working that's great
• The actual deployment is not the fastest but it's not too bad

Incentivized

We definitely need to renew it because we dont own our own infrastructure and storage and we are happy with Cloud Run features

Incentivized

I enjoy the fact that Azure App Service can be managed by the Azure portal and a fully graphical user interface, as well as from two different flavors of command-line interface, i.e. Azure CLI and Azure Powershell. By utilizing the Azure Cloud Shell, we are able to switch between Azure Bash (CLI) and Powershell at any given moment and manage the Azure App Service settings from devices of any form-factor (Web based management).

Incentivized

The UI/console is great... the documentation is top-notch for developers, but the CLI itself when you have to script around it is very complex and easy to forget some options... the downside of a generic command line client.

Incentivized

Not seen any major issues when we run applications its good

Incentivized

Initially we felt slow but slowly it picked up and easy to manage

Incentivized

We had an issue where we deployed too large of a resource and didn't notice until the bill came through. They were very understanding and saw we weren't utilizing the resources so they issued a generous refund in about 4 hours. Very fast, friendly, and understanding support reps from my experience.

Incentivized

I was involved in the initial implementation setup, Its easy with the given documentaiton we can do ourself. Not that critical

Incentivized

In terms of deploying your apps, Azure App Service provides a solid foundation. You may use either the Azure command-line interface or the Web Portal to administer these apps. As a whole, I find You may easily deploy your apps to Azure App Service to be a really difficult platform for novices to get their feet wet. First and foremost, I'd look at Heroku's user interface and the way it abstracts compute units.

Incentivized

AWS Lambda supports code zip package, enabling lower cold start time. Also, AWS Lambda pricing is much simpler, easier to understand.

Other than that, the 2 products are very similar, including the Docker image support: the image must be built based on proprietary base image.

Obviously, if your other services are running in GCP, then Google Cloud Run is your only choice for tight integration, & private networking.

Incentivized

It has good auto scale feature and reliable also

Incentivized

• Download time is reduced because of auto scaling feature.
• Insight tool helps in finding issues quickly.
• CI/CD has helped in automation.

Incentivized

• It has saved us some costs since we now do not require a live server and have moved to a serverless workflow for these services
• Breaking changes do not affect the entire application now that we have separated our concerns using a serverless service
• Much easier to debug since we can now isolate our services and reduce the search space for finding/fixing bugs

Incentivized