Mantenha tudo organizado com as coleções
Salve e categorize o conteúdo com base nas suas preferências.
ID da região
O REGION_ID é um código abreviado que o Google atribui
com base na região que você selecionou ao criar o aplicativo. O código não
corresponde a um país ou estado, ainda que alguns IDs de região sejam semelhantes
aos códigos de país e estado geralmente usados. Para apps criados após
fevereiro de 2020, o REGION_ID.r está incluído nos
URLs do App Engine. Para apps existentes criados antes dessa data, o
ID da região é opcional no URL.
É possível usar vários métodos para se comunicar entre seus serviços do App Engine
ou com outros serviços, incluindo serviços do Google Cloud e
aplicativos externos.
A abordagem mais simples para a comunicação com o serviço do App Engine é
enviar solicitações HTTP segmentadas, em que o URL inclui o nome ou o ID de um
recurso. Por exemplo, inclua o ID de um serviço ou versão que
quer segmentar, além do ID do projeto do Google Cloud correspondente:
Para compartilhar dados entre bancos de dados e o aplicativo do App Engine ou outro
aplicativo externo, consulte
Noções básicas sobre armazenamento de dados e
arquivos.
No ambiente padrão, também é possível passar solicitações entre serviços e de
serviços para endpoints externos com a API
URL Fetch.
Além disso, os serviços no ambiente padrão que residem no mesmo projeto do Google Cloud também
podem usar uma das APIs do App Engine
nas tarefas a seguir:
[[["Fácil de entender","easyToUnderstand","thumb-up"],["Meu problema foi resolvido","solvedMyProblem","thumb-up"],["Outro","otherUp","thumb-up"]],[["Difícil de entender","hardToUnderstand","thumb-down"],["Informações incorretas ou exemplo de código","incorrectInformationOrSampleCode","thumb-down"],["Não contém as informações/amostras de que eu preciso","missingTheInformationSamplesINeed","thumb-down"],["Problema na tradução","translationIssue","thumb-down"],["Outro","otherDown","thumb-down"]],["Última atualização 2024-12-22 UTC."],[[["\u003cp\u003eThe REGION_ID is a code assigned by Google based on the region selected when creating an app, included in App Engine URLs for apps created after February 2020.\u003c/p\u003e\n"],["\u003cp\u003eApp Engine services can communicate through targeted HTTP requests using URLs that include the service or version ID and project ID.\u003c/p\u003e\n"],["\u003cp\u003eData can be shared across databases, App Engine apps, and external applications using methods outlined in the "Understanding Data and File Storage" documentation.\u003c/p\u003e\n"],["\u003cp\u003eWithin the same Google Cloud project, App Engine services can share a memcache instance and collaborate using Task Queues via specific APIs.\u003c/p\u003e\n"],["\u003cp\u003eCertain URL paths are restricted and cannot be used, including those ending with \u003ccode\u003e/eventlog\u003c/code\u003e, starting with \u003ccode\u003e/_ah/\u003c/code\u003e, and some ending with \u003ccode\u003ez\u003c/code\u003e.\u003c/p\u003e\n"]]],[],null,["# Communicating Between Your Services\n\n### Region ID\n\nThe \u003cvar translate=\"no\"\u003eREGION_ID\u003c/var\u003e is an abbreviated code that Google assigns\nbased on the region you select when you create your app. The code does not\ncorrespond to a country or province, even though some region IDs may appear\nsimilar to commonly used country and province codes. For apps created after\nFebruary 2020, \u003cvar translate=\"no\"\u003eREGION_ID\u003c/var\u003e`.r` is included in\nApp Engine URLs. For existing apps created before this date, the\nregion ID is optional in the URL.\n\nLearn more\n[about region IDs](/appengine/docs/legacy/standard/java/how-requests-are-routed#region-id). \nOK\n\nYou can use various methods to communicate between your App Engine\nservices or with other services, including Google Cloud services and\nexternal applications.\n\nThe simplest approach for communicating with your App Engine service is\nto send targeted HTTP requests, where the URL includes the name or ID of a\nresource. For example, you can include the ID of a service or version that you\nwant to target, in addition to the corresponding Google Cloud project ID: \n\n\n https://\u003cvar translate=\"no\"\u003eVERSION\u003c/var\u003e-dot-\u003cvar translate=\"no\"\u003eSERVICE\u003c/var\u003e-dot-\u003cvar translate=\"no\"\u003ePROJECT_ID\u003c/var\u003e.\u003cvar translate=\"no\"\u003e\u003ca href=\"#appengine-urls\" style=\"border-bottom: 1px dotted #999\" class=\"devsite-dialog-button\" data-modal-dialog-id=\"regional_url\" track-type=\"progressiveHelp\" track-name=\"modalHelp\" track-metadata-goal=\"regionalURL\"\u003eREGION_ID\u003c/a\u003e\u003c/var\u003e.r.appspot.com\n\nFor details about targeting your services, including how to define HTTPS URLs,\nsee [How Requests are\nRouted](/appengine/docs/legacy/standard/java/how-requests-are-routed).\nTo authorize the requests between your services and other Google Cloud\nservices, see [Setting Up Authentication for Server to Server Production\nApplications](/docs/authentication/production).\n\nTo share data across databases and your App Engine app or some other\nexternal application, see\n\n[Understanding Data and File\nStorage](/appengine/docs/legacy/standard/java/using-third-party-databases).\n\n\nIn the standard environment, you can also pass requests between services and\nfrom services to external endpoints using the\n[URL Fetch](/appengine/docs/legacy/standard/java/issue-requests) API.\n\nAdditionally, services in the standard environment that reside within the same\nGoogle Cloud project can also use one of the App Engine APIs for the\nfollowing tasks:\n\n- Share a single [memcache](/appengine/docs/legacy/standard/java/memcache) instance.\n- Collaborate by assigning work between services through [Task Queues](/appengine/docs/legacy/standard/java/taskqueue).\n\nReserved URL paths\n------------------\n\nIt is not possible to use the following URL paths:\n\n- Paths ending with `/eventlog`\n- Paths starting with `/_ah/`\n- Some paths ending with `z`"]]
