应用程序引擎为开发人员提供了控制谷歌计算引擎核心的能力，以及为谷歌计算引擎数据处理应用程序提供面向web的前端。

另一方面，计算引擎提供直接和完整的虚拟机操作系统管理。要呈现你的应用程序，你需要资源，而谷歌云存储是存储你的资产和数据的理想选择，无论它们是用来做什么。通过在全球各地托管，您可以快速访问数据。可靠性在99.95%的正常运行时间得到保证，谷歌还提供了备份和恢复数据的能力，信不信由你，存储是无限的。

您可以使用谷歌云存储管理您的资产，存储，检索，显示和删除它们。您还可以快速读写保存在云存储中的平面数据表。谷歌云阵容中的下一个是BigQuery。使用BigQuery，你可以在几秒钟内分析大量数据，我们说的是数百万条记录。访问是通过直接的UI或具象状态传输或REST接口来处理的。

正如您可能怀疑的那样，数据存储不是问题，而且可以扩展到数百TB。BigQuery可以通过一系列客户端库访问，包括Java、。net、Python、Go、Ruby、PHP和Javascript的客户端库。可以通过这些客户端库或web用户界面访问类似sql的语法NoSQL。最后，让我们谈谈谷歌云平台数据库选项，云SQL和云数据存储。

这里有一个主要的区别。云SQL适用于关系数据库，主要是MySQL，而云数据存储适用于使用noSQL的非关系数据库。使用Cloud SQL，您可以选择在美国、欧洲或亚洲托管，每个数据库实例有100gb的存储空间和16gb的RAM。

云数据存储免费提供每月最多50 K的读/写指令和每月存储1 GB的数据。但是，如果您超过了这些配额，就需要支付费用。App Engine还可以与谷歌云平台的其他不太知名、更有目标的成员合作，包括用于创建API后端的云端点，用于数据分析和趋势预测的谷歌预测API，或用于多语言输出的谷歌翻译API。

虽然你可以用App Engine自己做相当多的事情，但当你考虑到它能够轻松高效地与其他谷歌云平台服务一起工作时，它的潜力就会飙升。

谷歌计算引擎(GCE)

托管在云中的虚拟机(vm)。在云技术出现之前，这些服务器通常被称为虚拟专用服务器(VPS)。您可以像使用物理服务器一样使用这些服务器，在其中安装和配置操作系统，安装应用程序，安装数据库，保持操作系统的最新状态，等等。这被称为基础设施即服务(IaaS)。

当您在数据中心的VM或服务器上运行现有应用程序，并希望轻松地将其迁移到GCP时，VM最有用。

谷歌应用引擎

App Engine托管并运行你的代码，而不需要你处理操作系统、网络，以及许多你必须在物理服务器或VM上管理的其他事情。可以把它看作一个运行时，它可以自动部署、版本化和扩展应用程序。这被称为平台即服务(PaaS)。

当你想要自动部署和自动扩展你的应用程序时，App Engine是最有用的。除非应用程序需要自定义操作系统配置，否则App Engine通常比手动配置和管理虚拟机更有优势。

如果你熟悉其他流行的服务:

谷歌计算引擎-> AWS EC2

谷歌应用程序引擎-> Heroku或AWS弹性豆茎

谷歌云函数-> AWS Lambda函数

基本区别是谷歌应用程序引擎(GAE)是平台即服务(PaaS)，而谷歌计算引擎(GCE)是基础设施即服务(IaaS)。

To run your application in GAE you just need to write your code and deploy it into GAE, no other headache. Since GAE is fully scalable, it will automatically acquire more instances in case the traffic goes higher and decrease the instances when traffic decreases. You will be charged for the resources you really use, I mean, you will be billed for the Instance-Hours, Transferred Data, Storage etc your app really used. But the restriction is, you can create your application in only Python, PHP, Java, NodeJS, .NET, Ruby and **Go.

另一方面，GCE以虚拟机的形式为您提供完整的基础设施。您可以完全控制这些虚拟机的环境和运行时，因为您可以在其中编写或安装任何程序。实际上，GCE是虚拟使用谷歌数据中心的方式。在GCE中，您必须使用负载均衡器手动配置基础设施来处理可伸缩性。

GAE和GCE都是谷歌云平台的一部分。

更新:2014年3月谷歌在应用引擎下宣布了一项名为托管虚拟机的新服务。托管虚拟机在应用平台、CPU和内存选项上为应用引擎应用程序提供了更多的灵活性。像GCE一样，您可以在这些虚拟机中为应用程序引擎应用程序创建自定义运行时环境。实际上，App Engine的托管虚拟机在一定程度上模糊了IAAS和PAAS之间的界限。

简单地说:计算引擎给你一个服务器，你可以完全控制/负责。你可以直接访问操作系统，安装你想要的所有软件，通常是web服务器、数据库等……

在应用引擎中，你不需要管理任何底层软件的操作系统。你只需要上传代码(Java, PHP, Python或Go)，瞧——它就会运行……

应用引擎节省了大量的头痛，特别是对于没有经验的人，但它有2个显著的缺点: 1. 更贵(但它有一个计算引擎没有的免费配额) 2. 您的控制更少，因此某些事情是不可能的，或者只能以一种特定的方式实现(例如保存和写入文件)。

In addition to the App Engine vs Compute Engine notes above the list here also includes a comparison with Google Kubernete Engine and some notes based on experience with a wide range of apps from small to very large. For more points see the Google Cloud Platform documentation high level description of features in App Engine Standard and Flex on the page Choosing an App Engine Environment. For another comparison of deployment of App Engine and Kubernetes see the post by Daz Wilkin App Engine Flex or Kubernetes Engine.

应用引擎标准

Pros

Very economical for low traffic apps in terms of direct costs and also the cost of maintaining the app. Auto scaling is fast. Autoscaling in App Engine is based on lightweight instance classes F1-F4. Version management and traffic splitting are fast and convenient. These features are built into App Engine (both Standard and Flex) natively. Minimal management, developers need focus only on their app. Developers do not need to worry about managing VMs in a reliable, as in GCE, or learning about clusters, as with GKE. Access to Datastore is fast. When App Engine was first released, the runtime was co-located with Datastore. Later Datastore was split out as the standalone product Cloud Datastore but the co-location of App Engine Standard serving with Datastore remains. Access to Memcache is supported. The App Engine sandbox is very secure. Compared with development on GCE or other virtual machines, where you need to do your own diligence to prevent the virtual machine from being taken over at the operating system level, the App Engine Standard sandbox is relatively secure by default.

Cons

实例通常比其他环境更受约束 小。虽然这对快速自动缩放很有好处，但许多应用程序都可以 受益于更大的实例，例如GCE实例大小可达96 内核。 网络没有与GCE集成 不能把应用引擎后面的谷歌云负载均衡器。局限于 支持的运行时:Python 2.7, Java 7和8,Go 1.6-1.9和PHP 5.5. 在Java中，有一些对servlet的支持，但不支持完整的J2EE标准。

App Engine Flex

Pros

可以使用自定义运行时吗 本机集成GCE网络 版本和流量管理方便，与标准相同 较大的实例大小可能更适合大型复杂应用程序，特别是可能使用大量内存的Java应用程序

Cons

网络集成不完善——没有与内部负载均衡器或共享虚拟私有云集成 对托管Memcache的访问通常不可用

谷歌Kubernetes引擎

Pros

Native integration with containers allows custom runtimes and greater control over cluster configuration. Embodies many best practices working with virtual machines, such as immutable runtime environments and easy ability to roll back to previous versions Provides a consistent and repeatable deployment framework Based on open standards, notably Kubernetes, for portability between clouds and on-premises. Version management can accomplished with Docker containers and the Google Container Registry

Cons

Traffic splitting and management is do-it-yourself, possibly leveraging Istio and Envoy Some management overhead Some time to ramp up on Kubernetes concepts, such as pods, deployments, services, ingress, and namespaces Need to expose some public IPs unless using Private Clusters, now in beta, eliminate that need but you still need to provide access to locations where kubectl commands will be run from. Monitoring integration not perfect While L3 internal load balancing is supported natively on Kubernetes Engine, L7 internal load balancing is do-it-yourself, possibly leveraging Envoy

计算引擎

Pros

Easy to ramp up - no need to ramp up on Kubernetes or App Engine, just reuse whatever you know from previous experience. This is probably the main reason for using Compute Engine directly. Complete control - you can leverage many Compute Engine features directly and install the latest of all your favorite stuff to stay on the bleeding edge. No need for public IPs. Some legacy software may be too hard to lock down if anything is exposed on public IPs. You can leverage the Container-Optimized OS for running Docker containers

Cons

Mostly do-it-yourself, which can be challenging to do adequately for reliability and security, although you can reuse solutions from various places, including the Cloud Launcher. More management overhead. There are many management tools for Compute Engine but they will not necessarily understand how you have deployed your application, like the App Engine and Kubernetes Engine monitoring tools do Autoscaling is based on GCE instances, which can be slower than App Engine Tendency is to install software on snowflake GCE instances, which can be some effort to maintain