Communicating Between Your Services

You can use various methods to communicate between your App Engine services or with other services, including GCP services and external applications.

The simplest approach for communicating with your App Engine service is to send targeted HTTP requests, where the URL includes the name or ID of a resource. For example, you can include the ID of a service or version that you want to target, in addition to the corresponding GCP project ID:

http://[VERSION_ID].[SERVICE_ID].[MY_PROJECT_ID].appspot.com
https://[VERSION_ID]-dot-[SERVICE_ID]-dot-[MY_PROJECT_ID].appspot.com

For details about targeting your services, including how to define HTTPS URLs, see How Requests are Routed. To authorize the requests between your services and other GCP services, see Setting Up Authentication for Server to Server Production Applications.

To share data across databases and your App Engine app or some other external application, see Understanding Data and File Storage. In the standard environment, you can also pass requests between services and from services to external endpoints using the URL Fetch API.

Additionally, services in the standard environment that reside within the same GCP project can also use one of the App Engine APIs for the following tasks:

  • Share a single memcache instance.
  • Collaborate by assigning work between services through Task Queues.
هل كانت هذه الصفحة مفيدة؟ يرجى تقييم أدائنا:

إرسال تعليقات حول...

App Engine standard environment for Python 2