简体   繁体   English

在App Engine标准和Kubernetes(容器引擎)之间选择

[英]Deciding between App Engine Standard and Kubernetes(Container Engine)

We are going to start an open source project on GitHub. 我们将在GitHub上启动一个开源项目。

We are going to use Microservices Architecture for this and the language for this is going to use is Java 我们将为此使用微服务架构 ,并且将使用的语言是Java

And we are going to use Google Cloud endpoints v2 in java for all these services. 我们将在Java中将Google Cloud端点v2用于所有这些服务。

There are almost 12 services which work together to make a big API. 几乎有12种服务可以共同构成一个大型API。

Every service serves its own API which is created in cloud endpoints but some services need to communicate with each other to function properly. 每个服务都提供自己的API,该API是在cloud endpoints点中创建的,但是某些服务需要相互通信才能正常运行。

We have one problem we are not able to decide which fit best for this situation for this. 我们有一个问题,我们目前无法决定哪种方式最适合这种情况。 AppEngine standard or Khubernetes(Container Engine) ? AppEngine标准还是Khubernetes(容器引擎)

We take many presentations of Google Cloud Platform about deciding this but not able to decide. 关于Google Cloud Platform的决定,我们进行了许多演示,但无法确定。 Can you please let me know which is good for this and why. 您能告诉我哪个对这个有好处,为什么。 This project is going for a long time. 这个项目进行了很长时间。

If your application runs in containers I would probably go for Kubernetes but the decission might vary based on your use-case. 如果您的应用程序在容器中运行,我可能会选择Kubernetes但是根据您的用例,决定可能会有所不同。

If you are not afraid of handling your infrastructure and you want to define your own resources, rules etc., then Kubernetes offers more flexibility. 如果您不怕处理基础架构,并且想定义自己的资源,规则等,那么Kubernetes提供更大的灵活性。 You can pretty much define the whole application stack in one YAML file and in case Google Cloud Platform turns out not to be the best solution for you, you can easily spin the Kubernetes cluster elsewhere. 您几乎可以在一个YAML文件中定义整个应用程序堆栈,并且如果Google Cloud Platform证明不是您的最佳解决方案,则可以轻松地将Kubernetes集群旋转到其他位置。

AppEngine is basically PaaS solution focused on application development where you delegate most of the infrastructure decisions to Google. AppEngine基本上是PaaS解决方案,专注于应用程序开发,您可以在其中将大多数基础架构决策委托给Google。 You can get the application running and scaling with minimum fuss. 您可以以最小的麻烦让应用程序运行和扩展。

One of the other aspects to consider is also the pricing. 要考虑的其他方面之一也是定价。 Take a look at GCP price calculator . 看看GCP价格计算器 It might turn out that Kubernetes is significantly cheaper in case you have multiple services (you can all run them in a single cluster as opposed to getting billed per GAE application). 事实Kubernetes ,万一您有多种服务, Kubernetes会便宜很多(您可以将它们全部运行在一个集群中,而不是针对每个GAE应用程序GAE )。

声明:本站的技术帖子网页,遵循CC BY-SA 4.0协议,如果您需要转载,请注明本站网址或者原文地址。任何问题请咨询:yoyou2525@163.com.

 
粤ICP备18138465号  © 2020-2024 STACKOOM.COM