Go 1.11 has reached end of support
and will bedeprecatedon January 31, 2026. After deprecation, you won't be able to deploy Go 1.11
applications, even if your organization previously used an organization policy to
re-enable deployments of legacy runtimes. Your existing Go
1.11 applications will continue to run and receive traffic after theirdeprecation date. We
recommend that youmigrate to the latest supported version of Go.
Stay organized with collectionsSave and categorize content based on your preferences.
Historically, the App Engine standard environment provided several scalable,
proprietary services for app development. These services were bundled withfirst-generation runtimes(also called
App Enginelegacy runtimes), which includePython 2,Java 8,Go 1.11, andPHP 5.5. Because several
of the legacy runtimes are no longer maintained by their respective
open-source communities, as an App Engine developer, you may face hard choices
on whether to invest time and effort in migrating to a newer runtime or else
incur growing costs to retain your app on a legacy runtime.
Recognizing this challenge, Google Cloud is committed to providing you with a
more incremental migration path to newer runtimes. To reduce runtime migration
complexity, Google Cloud now supports a set of App Engine legacy bundled services and
their associated APIs on second-generation runtimes, which includePython 3,Java 11,Go 1.12+, andPHP 7/8. Your app
can call legacy bundled services APIs for second-generation runtimes through
language-idiomatic libraries.
Figure 1.How apps access the App Engine legacy bundled services
In runtime migration scenarios, you often also have the option to use
Google Cloud products that offer similar functionality as the
legacy bundled services. For the legacy bundled services that are not available as
separate products in Google Cloud, such as image processing, search, and
messaging, you can use third-party providers or other workarounds as suggested
in theRuntimes guide.
[[["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-09-04 UTC."],[[["\u003cp\u003eApp Engine's standard environment historically offered scalable, proprietary services bundled with first-generation runtimes like Python 2, Java 8, Go 1.11, and PHP 5.5.\u003c/p\u003e\n"],["\u003cp\u003eDue to the lack of maintenance for some legacy runtimes, developers face the decision of migrating to newer runtimes or bearing increasing costs to maintain apps on legacy versions.\u003c/p\u003e\n"],["\u003cp\u003eGoogle Cloud now supports App Engine legacy bundled services and their APIs on second-generation runtimes, including Python 3, Java 11, Go 1.12+, and PHP 7/8, simplifying the migration process.\u003c/p\u003e\n"],["\u003cp\u003eDevelopers migrating to newer runtimes can either use Google Cloud products that mirror legacy services or, for services not available, they can explore third-party alternatives or other workarounds.\u003c/p\u003e\n"]]],[],null,["# Overview of legacy bundled services\n\nHistorically, the App Engine standard environment provided several scalable,\nproprietary services for 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\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/8](/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](/appengine/docs/standard/runtimes).\n\n\u003cbr /\u003e\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).\nIf you need to access the App Engine legacy bundled services when migrating to second-generation runtimes,\nsee [Access legacy bundled services for Go 1.12+](/appengine/docs/standard/go/services/access).\n\n\u003cbr /\u003e\n\n\u003cbr /\u003e"]]
