Most of the functionality provided by the App Engine bundled services is now provided by the Cloud Client Libraries for Go. For more information, see the recommended alternatives listed below.
If migrating to an unbundled solution is not an option for your project, then you may be able to continue using App Engine bundled services in your Go 1.12+ apps as a fallback. This approach gives you flexibility to move to unbundled services later in the migration cycle.
- Use Cloud Tasks to enqueue tasks
from Go 1.12 and newer using the
cloudtaskspackage. You can use any App Engine service as the target of an App Engine task.
- Instead of the App Engine Mail API, use a third-party mail provider such as SendGrid, Mailgun, or Mailjet to send email. All of these services offer APIs to send email from applications.
- To cache application data, use Memorystore for Redis.
Access the App Engine Modules API using the
google-api-go-clientlibrary. Use the environment variables and the App Engine Admin API to obtain information and modify your application's running services:
Service information How to access Current service name
Current service version
Current instance ID
Default hostname Admin API
List of services Admin API
List of versions for a service Admin API
Default version for a service, including any traffic splits Admin API
List of running instances for a version Admin API
Instead of using the App Engine Search API, host any full-text search database such as ElasticSearch on Compute Engine and access it from your service.
Use similar functionalities provided by the App Engine Images API in Cloud Storage through the
storagepackage and a third-party service to manipulate images. To get started, see the Cloud Storage Client Libraries page.
The following App Engine-specific functionalities have been superseded by the Go standard library packages listed below:
App Engine package Go standard library package