Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Showing content from https://cloud.google.com/appengine/docs/standard/python/migrate-to-python3/migrating-services below:

Migrate off of legacy bundled services | App Engine migration center

Stay organized with collections Save and categorize content based on your preferences.

Most of the functionality provided by the legacy bundled services is now provided by the Cloud Client Libraries. 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 legacy bundled services in your apps as a fallback. This approach gives you flexibility to move to unbundled services later in the migration cycle.

After you migrate off of legacy bundled services, you can continue using App Engine or migrate to Cloud Run. Cloud Run is designed to improve upon the App Engine experience, and incorporates many of the best features of both the standard environment and the flexible environment. To compare features and understand how to migrate, see the App Engine and Cloud Run comparison guide.

To store and retrieve data, use Cloud Storage through the Cloud Client Libraries. To get started, see Using Cloud Storage.

You can serve images from Cloud Storage, serve them directly, or use a third-party content delivery network (CDN).

The App Engine Images service also provided functionality to avoid dynamic requests to your application by handling image resizing using a serving URL. If you want similar functionality, you can generate the re-sized images ahead of time and upload them to Cloud Storage for serving. Alternatively, you could use a third-party content delivery network (CDN) service that offers image resizing.

We recommend that you update your app to use Cloud Logging, which supports features such as viewing logs in the Logs Explorer, downloading logs, filtering messages by severity, and correlating app messages with specific requests. Alternatively, if you prefer simplicity over data accuracy, you can write structured logs to stdout or stderr. For more information, see Writing and viewing logs.

To send email, use a third-party mail provider such as SendGrid, Mailgun, or Mailjet. All of these services offer APIs to send emails from applications. A recommended third-party alternative for inbound messaging is not available at this time.

To cache application data, use Memorystore for Redis.

To obtain information and modify your application's running services, use a combination of environment variables and the App Engine Admin API:

For more information about the data available about your application's running services, see runtime environment.

Instead of using the App Engine OAuth service to verify OAuth 2.0 tokens, use the oauth2.tokeninfo method of the OAuth 2.0 API.

Host any full-text search database such as Elasticsearch on Compute Engine and access it from your service.

Queue tasks for asynchronous code execution using the Cloud Tasks REST API, RPC API, or the Cloud Client Libraries, and use a App Engine standard service as a Push target. For more information, see Migrating from Task Queues to Cloud Tasks.

In many cases where you might use pull queues, such as queuing up tasks or messages that will be pulled and processed by separate workers, Pub/Sub can be a good alternative as it offers similar functionality and delivery guarantees.

For an alternative to the Users API, use any of the HTTP-based authentication mechanisms described on the User authentication page.

Except as otherwise noted, the content of this page is licensed under the Creative Commons Attribution 4.0 License, and code samples are licensed under the Apache 2.0 License. For details, see the Google Developers Site Policies. Java is a registered trademark of Oracle and/or its affiliates.

Last updated 2025-07-09 UTC.

[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Hard to understand","hardToUnderstand","thumb-down"],["Incorrect information or sample code","incorrectInformationOrSampleCode","thumb-down"],["Missing the information/samples I need","missingTheInformationSamplesINeed","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-07-09 UTC."],[[["Most functionalities from legacy bundled services are now provided by Cloud Client Libraries, offering a modern approach to App Engine development."],["If unbundled solutions are not immediately feasible, you can still use legacy bundled services as a temporary fallback, allowing a phased migration to newer services."],["After migrating away from legacy bundled services, consider transitioning from App Engine to Cloud Run, which enhances the App Engine experience with improved features."],["For services like Blobstore, Datastore, Images, Logging, Mail, Memcache, Search, and Task Queues, use recommended Google Cloud or third-party alternatives, detailed within the document."],["To obtain information and modify your application's running services, you can utilize environment variables in conjunction with the App Engine Admin API, as the document clearly presents the way to do so for each service."]]],[]]

RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4