Google App Engine is Google Cloud's platform-as-a-service offering. It features pay-per-use pricing and support for a broad array of programming languages.
$0.05
Per Hour Per Instance
Google Compute Engine
Score 8.8 out of 10
N/A
Google Compute Engine is an infrastructure-as-a-service (IaaS) product from Google Cloud. It provides virtual machines with carbon-neutral infrastructure which run on the same data centers that Google itself uses.
$0.01
Hour
Pricing
Google App Engine
Google Compute Engine
Editions & Modules
Starting Price
$0.05
Per Hour Per Instance
Max Price
$0.30
Per Hour Per Instance
Preemptible Price - Predefined Memory
0.000892 / GB
Hour
Three-year commitment price - Predefined Memory
$0.001907 / GB
Hour
One-year commitment price - Predefined Memory
$0.002669 / GB
Hour
On-demand price - Predefined Memory
$0.004237 / GB
Hour
Preemptible Price - Predefined vCPUs
0.006655 / vCPU
Hour
Three-year commitment price - Predefined vCPUS
$0.014225 / CPU
Hour
One-year commitment price - Predefined vCPUS
$0.019915 / vCPU
Hour
On-demand price - Predefined vCPUS
$0.031611 / vCPU
Hour
Offerings
Pricing Offerings
Google App Engine
Google Compute Engine
Free Trial
No
Yes
Free/Freemium Version
Yes
Yes
Premium Consulting/Integration Services
No
No
Entry-level Setup Fee
No setup fee
No setup fee
Additional Details
—
Prices vary according to region (i.e US central, east, & west time zones). Google Compute Engine also offers a discounted rate for a 1 & 3 year commitment.
More Pricing Information
Community Pulse
Google App Engine
Google Compute Engine
Considered Both Products
Google App Engine
Verified User
Anonymous
Chose Google App Engine
simpler and cheaper sums up the benefits. AWS became too bureaucratic while Google App Engine made he process easier to setup. Again, I just spent a few minutes to setup a simple app, setup a budget, add my credit card and have it up and running. Google is captivating its user …
For our organization, we selected Google App Engine which provides a reliable and efficient way to create and deploy apps moreover it supports a lot of languages and provides automatic debugging of code which enables us to deploy code to production as soon as development is …
If you have a small team which is also responsible for development of the product then surely go for it. And if you have a larger team with dedicated person to take care of deployments. Go for cheaper options such as compute engine or AWS (be sure to do your research on pricing …
It's the manageability of the Google App Engine which made it a better option in our case. It's quite straightforward to deploy on App-Engine. No worries for monitoring setup
You can create and scale Kubernetes clusters quickly, but you have to keep an eye on that cluster. In-App Engine, you don't have to worry about infrastructure, but in some scenarios, Kubernetes fits better.
Google App Engine is the first product we picked up to store the mass data. Later we came to know that, firebase database is also similar to Google App Engine. But still, we didn't step into it. We will try it later.
Azure App Service is in par with Google App Engine although you may want to use Azure App Service if you are integrating with other Microsoft IT components, for example SQL Server. Google App Engine is great when in long run, you will be using Google cloud components, for …
App Engine is a much more streamlined system than EC2. There is a fundamental difference between them, but they are used for basically the same thing as far a I could tell -- to serve applications EC2 is certainly more complicated, but if offers more machine-level control if …
Google App Engine is very easy to use and mostly up to date makes it compatible with all old and new devices. The applications are very interactive and the prices are accessible for most users. The prices tend to get slightly expensive as we head on towards higher …
The two giants are Google and Amazon. Both are very similar however Google App Engine allows you to deploy your web applications through platforms like Python where as if you're using AWS, you have full control on the operating system services. Google is good because you pay as …
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 …
We commonly decide between App Service, Elastic Beanstalk, and App Engine. Normally, we do not have a strong preference for the services, it really comes down to whether or not there are other factors drawing us toward a particular platform. In the case of App Engine, it is a …
I think that Microsoft and Amazon are simply investing more in their offerings, and there are a bunch of cool PaaS solutions out there as well. Google App Engine is solid, and is probably the right choice for some projects. But ultimately one should evaluate each platform …
Google Apps is great for environments where the need for a more robust platform is not necessary if you are looking to have email and cloud collaboration enablement of your working staff. From the stand point of using both, I can see the value of both but it really depends on …
AWS and Heroku are both great, and I use them both extensively for different projects. Google App Engine was chosen because it is much more innovative than AWS, and because Heroku specializes in Ruby on Rails. Even though Heroku supports Java and other services, we feel Google …
With GAE it's a matter of "code your app and deploy it". You don't care on what servers or on how many servers it runs. System administration is done for you. With AWS you still have to be a system administrator with good knowledge and undestanding of load balancers, database …
You can spawn up your own cluster using Kubernetes or Container Engine which will scale automatically when configured properly, but you have to keep an eye on that cluster. In App Engine you don't have to worry about it at all, just ship your code and it will run.
We chose Google App Engine because it supplies the most infrastructure per dollar spent. It's much more expensive to use Amazon EC2 to scale to over a million users. Also, the engine's narrow language support system, while somewhat limiting, makes getting started quickly much …
We left Lotus Notes for the (more versatile) Google Apps. We could never recommend the closed architecture of Lotus Notes. We have evaluated Office 365 and believe the product is compelling. So compelling, that we may consider a platform change…
Rather than saying GCE is better. I would say that depends on the business and technical requirements it might fit better than others. There is no silver bullet.
I actually prefer Azure's UI over Google Compute Engine's , but Google Compute Engine's pricings are way more competitive, which makes it the go-to choice for infrastracture low budget companies such as ours, since our core business is not IT or software development related
Cloud providers offering virtual machines are quite common. I think, Google, however, is arguably one of the top players in the market, with some of the largest (if not the largest) and most advanced server farms in the world. If you're looking for reliability and cost …
The perfect blend of setup flexibility, costing and trust of Google could be my answer to the comparison. This being a server backed service so, ruling out the functions. The Setup flexibility and speed set the GCE apart from Kubernetes. Compliance, regulation and the security …
We have tried using DigitalOcean droplets for some of our minor and non critical VMs. In our experience, Google Compute Engine fares well in comparison the DigitalOcean droplets as they provide better availability, better support and in general, a better experience.
As far as user-friendliness is concerned, I personally rank Google Cloud above both AWS and Azure. Their user interface makes it easy to manage, which is important.
I find Google Compute Engine to be much easier to use than Amazon's EC2 service. The console makes much more sense, permission management is much cleaner, and I'd say the other categories feel on par with EC2: performance, how fine-grained the settings are, connecting to …
The obvious and natural alternatives to GCE are AWS EC2 and Azure VMs. I would say all three are more similar than not. Picking one will most likely depend on what platform you're on already, where your running services are, and which one is more familiar to your team.
When configuring Amazon ECS, it is a bit confusing as you are not able to find the actual issue. You need to enable Additional AppInsights to get detailed level info, which is not a concern when configuring on the Instance Level. Moreover, Azure VM does not provide an …
The Google Cloud computing engine is fair at the top because it bills customers, automatic discounting for extended use, and how fast it can be turned on. We enjoy things around setting it up very easily via APIs and CLI commands, and with the always-on recommendations from …
I have utilised Google Compute Engine in addition to Amazon EC2. Both exhibit excellent performance in terms of consumption, speed, and efficiency.My decision to adopt Google Compute Engine was solely based on how user-friendly it is. more basic UI/UX than EC2.Google's customer …
Google Compute Engine provides on-demand computing resources that are easy to scale up or down according to my organization needs. This allows our business to quickly adapt to changes in demand without having to invest in additional hardware. It also offers a very competitive …
While Amazon EC2 is the best tool for developers to build an app and make it live, It has some downsides too. EC2 requires so much development while Google Compute Engine makes it easy to build an app within a days. EC2 pricing also relatively high compare to Google Compute …
GCE is available in 3 different regions whereas Ec2 is available in 11 different regions. The compute resources offered by the GCE has lower maximum capacity compared to AWS Ec2. The pricing model of GCE offers first 10 mins free and then charging in increments of 10 mins. Both …
I prefer the Compute Engine Over these as it provides us with Better Scalability, Performance, and Reliability Security-related Issues don't arise with the Compute Engine, but yes, in terms of accessing or running, it can be improved a bit as compared to EC2 offered by AWS.
the main reason of choosing GCE is availability and user friendly UI with a very good documentation and API explanations. Great visibility over the infra and security.
The features specific to Google Compute Engine vs Amazon EC2 along with cost and availability are comparable, there may be other services within the vendor which may mean that one is more suitable for specific applications than the other one. We have used both for different …
Google App Engine and Google Compute Engine are both services businesses can use for deploying applications once they’ve been coded. Google App Engine is a platform-as-a-service solution designed to make app deployment as easy possible. In contrast, Google Compute Engine is an infrastructure-as-a-service tool that provides a highly configurable and flexible platform for application deployment. Both options are most popular with small businesses, but Google App Engine is more popular with larger businesses, likely due to its automation features.
Features
Google App Engine and Google Compute Engine both provide a platform for application deployment, but they also have some standout features that are important to consider.
Google App Engine provides a host of automation features that make it easy for businesses to focus on app development, instead of configuring the deployment. As applications deployed on Google App Engine see more or less use, the platform will automatically adjust the number of instances without input from a developer. Google App Engine also provides a software development kit to help users optimize applications for the platform.
Google Compute Engine allows for a high level of customization so users can set up their deployment however they want. Businesses with a skilled development team can create as many or as few virtual machines as they want, while customizing them for the needs of their applications. Google Compute Engine is also generally more affordable compared to Google App Engine, which can make it more appealing to businesses on a smaller budget.
Limitations
Google App Engine and Google Compute Engine both help businesses deploy their applications, but they also have a few limitations that are important to consider.
Google App Engine provides a high level of automation and is simple to use, but isn’t as customizable as Google Compute Engine. Businesses with specific needs for their application may prefer the customizability of Google Compute Engine. Additionally, while Google App Engine’s software development kit is great for applications that are developed with Google App Engine, it can be difficult to take advantage of it if for applications that were developed before Google App Engine was selected.
Google Compute Engine is highly customizable, but it isn’t as automated or easy to use. Businesses using Google Compute Engine will have to manually adjust the volume of their virtual machines as application traffic grows or shrinks. Google Compute engine needs a development team to work with it, unlike Google App Engine, which can be managed with less effort.
Pricing
Google App Engine pricing depends on the type of instance, but starts as low as $0.05 per hour per instance.
Google Compute Engine offers pay as you go pricing starting as low as $0.006543 per hour.
Features
Google App Engine
Google Compute Engine
Platform-as-a-Service
Comparison of Platform-as-a-Service features of Product A and Product B
Google App Engine
9.5
Ratings
20% above category average
Google Compute Engine
-
Ratings
Ease of building user interfaces
9.00 Ratings
00 Ratings
Scalability
10.00 Ratings
00 Ratings
Platform management overhead
9.00 Ratings
00 Ratings
Workflow engine capability
8.00 Ratings
00 Ratings
Platform access control
10.00 Ratings
00 Ratings
Services-enabled integration
10.00 Ratings
00 Ratings
Development environment creation
10.00 Ratings
00 Ratings
Development environment replication
10.00 Ratings
00 Ratings
Issue monitoring and notification
9.00 Ratings
00 Ratings
Issue recovery
9.00 Ratings
00 Ratings
Upgrades and platform fixes
10.00 Ratings
00 Ratings
Infrastructure-as-a-Service (IaaS)
Comparison of Infrastructure-as-a-Service (IaaS) features of Product A and Product B
Google App Engine is especially well suited for situations where there is a variable workload during the day, e.g. inbound task processing with task queues. In this situation queues can be setup with parameters governing the process speed/scaling which allows you to easily balance performance with cost and meet a good balance.
It is excellent if you have any workloads that need raw computing or plan to have any state-full services running in your environment like DBs (for which you don't want to use Managed services), cache, etc. It also gives you complete control over which versions of software, OS, etc., you need, and thus, you can build anything and deploy it on GCE.
Building an application that uses Google's Authentication, means users no longer need to remember an different user id and password. Once they are logged into to Google, they can seamlessly access your application hosted on Google App Engine.
Google App Engine automatically scales up and down. SO if your application receives a spike in user traffic, App Engine automatically launches additional instances of your application to cater for the increased traffic. Once App Engine detects that the spike is usage is over, it automatically scales down to handle the current traffic.
Google App Engine can be easily integrated with Google Cloud SQL, Google Compute Engine, Google Cloud Storage etc, so that you can build out a full application using one or more of Google's Cloud Platform products.
A simple web-based interface that is a breeze to train new engineers to use. Our experienced engineers never have trouble finding or doing anything on GCE.
Sustained use and Committed use discounts mean we get top-tier VMs for an incredibly competitive price.
Wonderful identity and access management that gives us peace-of-mind when granting access to machines to contractors and other 3rd parties.
Fast VMs, lastest in hardware, and enough RAM to power even the hungriest of our services.
The L7 load balancer can be difficult to get set up. It's limited in its functionality, especially with the container engine.
It's hard to find certain objects on the web console. Often times the things I need to get to are buried in advanced menus.
Google's decision to only support MySQL on their relational DB service means that I have to manage Postgres instances in Compute on my own, managing everything from storage to backups.
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.
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.
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
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.
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
Google Compute Engine usually delivers good and predictable performance for our self-hosted stack of applications. However, when running n8n heavy workflows, even with a tunned instance configuration in docker, performance usually peaks usually due to memory usage. We often need to upgrade memory when we have heavier data processing and workflows. Other than that, in a normal usage, we don't really have any problems
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.
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.
App Engine is a much more streamlined system than EC2. There is a fundamental difference between them, but they are used for basically the same thing as far a I could tell -- to serve applications EC2 is certainly more complicated, but if offers more machine-level control if that's what you need. It can tend to cost more as well. App Engine is far more straightforward but there are limitations if you need to change the environment. But even then, Google Compute Engine also compares to EC2 and stays within GCP.
When configuring Amazon ECS, it is a bit confusing as you are not able to find the actual issue. You need to enable Additional AppInsights to get detailed level info, which is not a concern when configuring on the Instance Level. Moreover, Azure VM does not provide an in-browser option; instead, it is Azure Bastion, but for that, you have to enable a dedicated subnet, which is a bit unnecessary.
Scalability means flexibility and less upfront costs
Can become expensive when hard set compute requirements are clear, but things like Spot VMs can help here too, or just having your own infrastructure and scaling up with Google. This is for more advanced cases though
Ramp up time is long, but after that it is quick to do many things and ROI is awesome