GCP
All of these are solutions which allow you to host your applications in the cloud. You can view them as a sort of spectrum of control/automatic management. There's also another thing to consider: App Engine comes in two environments, "Standard" and "Flexible".
So the spectrum ends up being:
-
App Engine Standard: limited runtimes (Python, Java, PHP, Go), very simple to get up and running, auto-scaled etc. Focused APIs designed specifically for App Engine.
-
App Engine Flexible: anything you can put in a container, auto-scaled etc.
-
Container Engine: you design your application in terms of micro-services, specify how they're scaled etc, but let Container Engine (the Google Cloud Platform implementation of Kubernetes ) perform the scaling
-
Compute Engine: Hosted VMs with benefits, basically. Some features such as live migration, auto scaling within Managed Instance Groups , but it's much more "bare metal" than the above.
Basically, you need to decide how "hands-on" you want to be. The more control you decide to take, the more work you have to do but the more precise tuning (and flexibility) you get.
Additionally, App Engine Standard supports "scale to zero" - if your app isn't getting any traffic, it can be completely dormant. That makes it a great environment for hobby projects.
來自 “ ITPUB部落格 ” ,連結:http://blog.itpub.net/26477398/viewspace-2214102/,如需轉載,請註明出處,否則將追究法律責任。
相關文章
- 在GCP的Kubernetes上安裝daprGC
- 讓Apache Beam在GCP Cloud Dataflow上跑起來ApacheGCCloud
- 使用 EMQX Cloud 橋接資料到 GCP Pub/SubMQCloud橋接GC
- 服務網格GCP (GKE, Istio, MSA) 搖滾組合GC
- 阿里雲挑戰AWS,Azure和GCP的6種方式阿里GC
- 在GCP上建立GCE的三種方式(Console,gcloud,Terraform)GCCloudORM
- window下通過Xshell登入GCP計算機例項GC計算機
- ENVI自動地理配準:GCP地面控制點的自動產生GC
- 《Terraform 101 從入門到實踐》 Terraform在公有云GCP上的應用ORMGC