Azure App Service vs. Google App Engine vs. Google Compute Engine

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

App Engine is such a good resource for our team both internally and externally. You have complete control over your app, how it runs, when it runs, and more while Google handles the back-end, scaling, orchestration, and so on. If you are serving a tool, system, or web page, it's perfect. If you are serving something back-end, like an automation or ETL workflow, you should be a little considerate or careful with how you are structuring that job. For instance, the Standard environment in Google App Engine will present you with a resource limit for your server calls. If your operations are known to take longer than, say, 10 minutes or so, you may be better off moving to the Flexible environment (which may be a little more expensive but certainly a little more powerful and a little less limited) or even moving that workflow to something like Google Compute Engine or another managed service.

Incentivized

You can use Google Cloud Compute Engine as an option to configure your Gitlab, GitHub, and Azure DevOps self-hosted runners. This allows full control and management of your runners rather than using the default runners, which you cannot manage. Additionally, they can be used as a workspace, which you can provide to the employees, where they can test their workloads or use them as a local host and then deploy to the actual production-grade instance.

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

• Quick to develop, quick to deploy. You can be up and running on Google App Engine in no time.
• Flexible. We use Java for some services and Node.js for others.
• Great security features. We have been consistently impressed with the security and authentication features of Google App Engine.

Incentivized

• Scaling - whether it's traffic spikes or just steady growth, Google Compute Engine's auto-scaling makes sure we've got the compute power we need without any manual juggling acts
• Load balancing - Keeping things smooth with that load balancing across multiple VMs, so our users don't have to deal with slow load times or downtime even when things get crazy busy
• Customizability - Mix and match configs for CPU, RAM, storage and whatnot to suit our specific app needs

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

• There is a slight learning curve to getting used to code on Google App Engine.
• Google Cloud Datastore is Google's NoSQL database in the cloud that your applications can use. NoSQL databases, by design, cannot give handle complex queries on the data. This means that sometimes you need to think carefully about your data structures - so that you can get the results you need in your code.
• Setting up billing is a little annoying. It does not seem to save billing information to your account so you can re-use the same information across different Cloud projects. Each project requires you to re-enter all your billing information (if required)

Incentivized

• Built-in monitoring via Stackdriver is quite expensive for what it provides.
• Initially provided quotas (ie. max compute units one can use) are very low and it took several requests to get an appropriate amount.
• Support on GCE is limited to their knowledge base and forums. For more hands-on support provided by Google, you must pay for their Premium services.

Incentivized

App Engine is a solid choice for deployments to Google Cloud Platform that do not want to move entirely to a Kubernetes-based container architecture using a different Google product. For rapid prototyping of new applications and fairly straightforward web application deployments, we'll continue to leverage the capabilities that App Engine affords us.

Incentivized

Its pretty good, easy and good performance. Also, interface is very good for starters compared to competitors. Infra as Code (IaC) using Terraform even added easiness for creation, management and deletion of compute Virtual Machines (VM). Overall, very good and very easy cloud based compute platform which simplified infrastructure, very much recommend.

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

I had to revisit the UI after a year of just setting up and forgetting. The UI got some improvements but the amount of navigation we have to go through to setup a new app has increased but also got easier to setup. Gemini now is integrated and make getting answers faster

Incentivized

Having interacted with several cloud services, GCE stands out to me as more usable than most. The naming and locating of features is a little more intuitive than most I've interacted with, and hinting is also quite helpful. Getting staff up to speed has proven to be overall less painful than others.

Incentivized

Google Compute Engine works well for cloud project with lesser geographical audience. It sometimes gives error while everything is set up perfectly. We also keep on check any updates available because that's one reason of site getting down. Google Compute Engine is ultimately a top solution to build an app and publish it online within a few minutes

Incentivized

It works great all the time except for occasional issues, but overall, I am very happy with the performance. It delivers on the promise it makes and as per the SLAs provided. Networking is great with a premium network, and AZs are also widespread across geographies. Overall, it is a great infra item to have, which you can scale as you want.

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

Good amount of documentation available for Google App Engine and in general there is large developer community around Google App Engine and other products it interacts with. Lastly, Google support is great in general. No issues so far with them.

Incentivized

• The documentation needs to be better for intermediate users - There are first steps that one can easily follow, but after that, the documentation is often spotty or not in a form where one can follow the steps and accomplish the task. Also, the documentation and the product often go out of sync, where the commands from the documentation do not work with the current version of the product.
• Google support was great and their presence on site was very helpful in dealing with various issues.

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

We were on another much smaller cloud provider and decided to make the switch for several reasons - stability, breadth of services, and security. In reviewing options, GCP provided the best mixtures of meeting our needs while also balancing the overall cost of the service as compared to the other major players in Azure and AWS.

Incentivized

Google Compute Engine provides a one stop solution for all the complex features and the UI is better than Amazon's EC2 and Azure Machine Learning for ease of usability. It's always good to have an eco-system of products from Google as it's one of the most used search engine and IoT services provider, which helps with ease of integration and updates in the future.

Incentivized

It works really well with other Google Cloud services, making it easy to build scalable solutions across different teams and locations.

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

• Effective employee adoption through ease of use.
• Effective integration to other java based frameworks.
• Time to market is very quick. Build, test, deploy and use.
• The GAE Whitelist for java is an important resource to know what works and what does not. So use it. It would also be nice for Google to expand on items that are allowed on GAE platform.

Incentivized

• With Google Compute we don't have the overhead of managing our own data centers reducing costs and reducing the staff needed to manage systems.
• As I said earlier, Google's costs are ~1/2 of AWS, so we are able to see a ROI much faster.

Incentivized