默认服务在Google应用引擎中的作用是什么 [英] What purpose does the default service serve in Google's app engine

问题描述

将具有微服务架构的应用程序部署到Google的应用程序引擎时，它需要我的一项服务才能成为默认服务.

When deploying an app with a microservices architecture to google's app engine, it requires one of my services to be the default service.

为什么要这样做，并且默认服务的行为与其他任何命名"服务有所不同?

Why is this required and does the default service behave any differently to any other 'named' service?

推荐答案

以下是default服务的一些角色/原因(我很确定列表并不详尽):

Here would be some roles/reasons for the default service (I'm fairly sure the list is not exhaustive):

• 如果没有匹配的路由规则，则使用dispatch.yaml文件路由请求的后备目的地
• cron作业的后备目的地(如果未将它们专门配置为针对特定服务的话)
• 有关应用程序级别配置的初始部署，请参见

• the fallback destination for routing a request using a dispatch.yaml file if none of the routing rules is matched
• the fallback destination for cron jobs if they aren't specifically configured to target a specific service
• for initial deployment of app-level configs, see Why do I need to deploy a "default" app before I can deploy multiple services in GCP?

实际上，我认为这种区别只是与命名服务相比是额外的功能(主要是与基础设施有关)，否则它们非常相似.

Practically I'd consider such differences just extra functionality (mostly infra-related) compared to the named services, otherwise they're very similar.

这篇关于默认服务在Google应用引擎中的作用是什么的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！