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.

Your App Engine services can also communicate using Cloud Pub/Sub, which provides reliable asynchronous many-to-many messaging between processes, including App Engine. These processes can be individual instances of your application, services, or even external applications.

To share data across databases and your App Engine app or some other external application, see Understanding Data and File Storage.

Оцените, насколько информация на этой странице была вам полезна:

Оставить отзыв о...

Текущей странице
App Engine flexible environment for Ruby docs