Mantieni tutto organizzato con le raccolte
Salva e classifica i contenuti in base alle tue preferenze.
In passato, l'ambiente standard di App Engine forniva diversi servizi proprietari scalabili per lo sviluppo di app. Questi servizi erano in bundle con
runtime di prima generazione
(chiamati anche
runtime legacy di App Engine), tra cui
Python 2,
Java 8,
Go 1.11 e
PHP 5.5. Poiché diversi runtime legacy non sono più gestiti dalle rispettive community open source, in qualità di sviluppatore App Engine potresti dover fare delle scelte difficili su come investire tempo e risorse per eseguire la migrazione a un runtime più recente o, in alternativa, sostenere costi crescenti per mantenere la tua app su un runtime legacy.
Consapevole di questa sfida, Google Cloud si impegna a fornirti un percorso di migrazione più incrementale ai runtime più recenti. Per ridurre la complessità della migrazione del runtime, Google Cloud ora supporta un insieme di servizi in bundle legacy di App Engine e le relative API associate sui runtime di seconda generazione, tra cui Python 3, Java 11 e versioni successive, Go 1.12 e versioni successive e PHP 7 e versioni successive. La tua app può chiamare le API dei servizi in bundle legacy per i runtime di seconda generazione tramite librerie idiomatiche del linguaggio.
Figura 1. In che modo le app accedono ai servizi in bundle legacy di App Engine
Negli scenari di migrazione del runtime, spesso hai anche la possibilità di utilizzare
Google Cloud prodotti che offrono funzionalità simili ai
servizi in bundle precedenti. Per i servizi integrati legacy che non sono disponibili come prodotti distinti in Google Cloud, come l'elaborazione di immagini, la ricerca e la messaggistica, puoi utilizzare fornitori di terze parti o altre soluzioni alternative come suggerito nella guida sui runtime.
[[["Facile da capire","easyToUnderstand","thumb-up"],["Il problema è stato risolto","solvedMyProblem","thumb-up"],["Altra","otherUp","thumb-up"]],[["Difficile da capire","hardToUnderstand","thumb-down"],["Informazioni o codice di esempio errati","incorrectInformationOrSampleCode","thumb-down"],["Mancano le informazioni o gli esempi di cui ho bisogno","missingTheInformationSamplesINeed","thumb-down"],["Problema di traduzione","translationIssue","thumb-down"],["Altra","otherDown","thumb-down"]],["Ultimo aggiornamento 2025-08-19 UTC."],[[["\u003cp\u003eApp Engine's standard environment historically offered proprietary services bundled with first-generation runtimes like Python 2, Java 8, Go 1.11, and PHP 5.5.\u003c/p\u003e\n"],["\u003cp\u003eGoogle Cloud acknowledges the challenges of migrating from legacy runtimes and now supports legacy bundled services and their APIs on second-generation runtimes, including Python 3, Java 11+, Go 1.12+, and PHP 7+.\u003c/p\u003e\n"],["\u003cp\u003eFor runtime migration, developers can either use App Engine's legacy bundled service APIs on newer runtimes, or utilize similar Google Cloud products.\u003c/p\u003e\n"],["\u003cp\u003eFor legacy services not offered as separate Google Cloud products, such as image processing, developers can explore third-party providers or other solutions.\u003c/p\u003e\n"]]],[],null,["# Overview of legacy bundled services\n\n\u003cbr /\u003e\n\n\u003cbr /\u003e\n\n\nHistorically, the App Engine standard environment provided several scalable, proprietary services\nfor app development. These services were bundled with\n[first-generation runtimes](/appengine/docs/standard/runtimes)\n(also called\nApp Engine *legacy runtimes* ), which include\n[Python 2](/appengine/docs/legacy/standard/python/runtime),\n[Java 8](/appengine/docs/legacy/standard/java/runtime),\n[Go 1.11](/appengine/docs/legacy/standard/go111/runtime), and\n[PHP 5.5](/appengine/docs/legacy/standard/php/runtime). Because several\nof the legacy runtimes are no longer maintained by their respective\nopen-source communities, as an App Engine developer, you may face hard choices\non whether to invest time and effort in migrating to a newer runtime or else\nincur growing costs to retain your app on a legacy runtime.\n\n\u003cbr /\u003e\n\nRecognizing this challenge, Google Cloud is committed to providing you with a\nmore incremental migration path to newer runtimes. To reduce runtime migration\ncomplexity, Google Cloud now supports a set of App Engine legacy bundled services and\ntheir associated APIs on second-generation runtimes, which include\n[Python 3](/appengine/docs/standard/python3/runtime),\n[Java 11+](/appengine/docs/standard/java-gen2/runtime),\n[Go 1.12+](/appengine/docs/standard/go/runtime), and\n[PHP 7+](/appengine/docs/standard/php-gen2/runtime). Your app\ncan call legacy bundled services APIs for second-generation runtimes through\nlanguage-idiomatic libraries.\n**Figure 1.** How apps access the App Engine legacy bundled services\n\nIn runtime migration scenarios, you often also have the option to use\nGoogle Cloud products that offer similar functionality as the\nlegacy bundled services. For the legacy bundled services that are not available as\nseparate products in Google Cloud, such as image processing, search, and\nmessaging, you can use third-party providers or other workarounds as suggested\nin the Runtimes guide.\n\nTo learn more about these options for migrating your app, see\n[Migrate off of legacy bundled services](/appengine/migration-center/standard/services/migrating-services)."]]
