Azure App Service vs. Google Cloud Run

You may easily deploy your apps to Azure App Service if they were written in Visual Studio IDE (typically.NET applications). With a few clicks of the mouse, you may already deploy your application to a remote server using the Visual Studio IDE. As a result of the portal's bulk and complexity, I propose Heroku for less-experienced developers.

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

• Extremely easy to deploy and update from Visual Studio
• It integrates seamlessly with other Azure PaaS resources
• It has an in-depth integration with AppInsights, so you can understand errors and their root cause easily.
• Easy to create and delete, what is not the same case in a IaaS resource
• It escalates based on CPU workload and some other resource variables.
• Configuration changes are almost immediate
• Offers an excellent abstraction from hardware backend of the platform
• That's updated very often, saving time and the risk of a self-performed update over a IaaS
• That's really easy to develop for Web Apps
• It supports Function Apps and Web Apps into the same "cost black box"

Incentivized

• Auto scaling is the best one
• provide direct VPC connectivity and rigid network
• Cloud SQL and Pub/Sub services
• Handling latency issues

Incentivized

• Jumps between resource sizes can get expensive
• You may wind up putting a lot of eggs in one basket--not necessarily a con but something to keep in mind (most of your data will likely be managed and processed through Microsoft products/services if you fully commit to Azure App Service).
• Learning new technology. If you're moving from on-premises to Azure App Service (or any cloud solutions), you'll likely have to rethink how things are done to achieve the same end results (and/or resources may become expensive quickly).

Incentivized

• The UI can be made simpler. Currently the UI is bloated and it takes time to find out what you want
• More integrations with container registry providers (ECR, dockerhub)
• Better permissions UX. Currently GCP requires service accounts to be used with cloud products, the experience adding/removing permissions is difficult to navigate

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 have given this rating because Azure App Service performs very well in terms of speed, reliability, and reducing overhead, and improves overall team productivity, with a little scope for improvement in complex testing scenarios and configurations, scalability concerns in a large setup, and similar tracking and audit needs.

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

Microsoft has always been known for providing a high standard in terms of customer support and Azure App Service (and as a matter of fact the whole Azure Platform) is no exception. Azure App Service never caused us any issues and we only contacted their customer support for questions regarding server locations and pricing. I feel pretty satisfied with how they treat their customers.

Incentivized

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

Incentivized

When we chose it, we did so because of its integration with Microsoft applications; now we need to integrate with AI, and Azure doesn't offer a good integration. That is the main reason to change it. It is still great to develop Windows- and Microsoft-based applications, but if we need to integrate with AI, Google wins by far.

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

Not part of purchase.

Incentivized

It has good auto scale feature and reliable also

Incentivized

We have very good support when needed

Incentivized

• Deployment of ASP.NET apps at the organization has been sped up.
• An option to offer access to the version control system on a third platform so that we could easily deploy our apps.
• Because of Azure App Service's scalability capabilities, the costs of running the services are kept to a minimum. As a result, we may save hundreds of dollars each month compared to the expenses of traditional servers by using fewer resources during slack periods.

Incentivized

• Built in support for auto scaling helps reduce operational overhead
• Any application performance issues can be addressed quickly by allocating more resources while a proper fix can be planned and rolled out later
• Using Google Cloud Run enables development of microservices which provides granular control for scaling critical services in the platform

Incentivized