[[["易于理解","easyToUnderstand","thumb-up"],["解决了我的问题","solvedMyProblem","thumb-up"],["其他","otherUp","thumb-up"]],[["很难理解","hardToUnderstand","thumb-down"],["信息或示例代码不正确","incorrectInformationOrSampleCode","thumb-down"],["没有我需要的信息/示例","missingTheInformationSamplesINeed","thumb-down"],["翻译问题","translationIssue","thumb-down"],["其他","otherDown","thumb-down"]],["最后更新时间 (UTC):2024-12-13。"],[],[],null,["# Deploy an enterprise developer platform on Google Cloud\n\nAs enterprises shift to container-based application development and deployment,\nthey must learn how to manage distributed teams with separate engineering\nworkflows. To help large enterprises complete the shift to container-based\napplications, we created the *enterprise application blueprint* . This blueprint\ndeploys an [internal developer platform](https://internaldeveloperplatform.org/)\nthat enables cloud platform teams to provide a managed platform for software\ndevelopment and delivery that their organization's application development\ngroups can use.\n\nThe enterprise application blueprint includes the following:\n\n- A [GitHub repository](https://github.com/GoogleCloudPlatform/terraform-google-enterprise-application) that contains a set of Terraform configurations and scripts. The Terraform configuration sets up a developer platform in Google Cloud that supports multiple development teams.\n- A guide to the architecture, design, security controls, and operational processes that you use this blueprint to implement (this document).\n\nThe enterprise application blueprint is designed to be compatible with the\n[enterprise foundations blueprint](/architecture/blueprints/security-foundations). The\nenterprise foundations blueprint provides a number of base-level services that\nthe enterprise application blueprint relies on, such as Cloud Identity. You\ncan deploy the enterprise application blueprint without deploying the enterprise\nfoundations blueprint if your Google Cloud environment provides the\n[necessary functionality to support the enterprise application blueprint](/architecture/blueprints/enterprise-application-blueprint/deploy-blueprint#deploy-without-efb).\n\nThis document is intended for cloud architects and assumes that you're using the\nenterprise application blueprint to deploy new enterprise applications on\nGoogle Cloud. However, if you already have existing containerized\nenterprise applications on Google Cloud, you can [incrementally adopt this reference architecture](/architecture/blueprints/enterprise-application-blueprint/deploy-blueprint#incorporate-the-blueprint-into-your-existing-gke-deployment).\n\nThis document also assumes that you understand Kubernetes components, including\nservices, namespaces and clusters. For background information on Kubernetes and\nits implementation in Google Cloud, see the [Google Kubernetes Engine (GKE) Enterprise edition technical overview](/anthos/docs/concepts/overview).\n\n### Enterprise application blueprint overview\n\nIn most enterprises, a developer platform manages the shared infrastructure that\nis used by all developers. The developer platform creates build pipelines,\ndeployment pipelines, and runtime environments for each application component on\ndemand. Developer teams and application operators have access to only those\napplication components for which they are responsible. The platform is designed\nto support the deployment of highly available and secure applications.\n\nThis blueprint deploys a developer platform on top of the enterprise foundations blueprint\n(or its equivalent). The developer platform includes resources such as\nGoogle Kubernetes Engine (GKE) clusters, GKE fleet, the application factory,\ninfrastructure pipelines, platform monitoring, and platform logging. In\naddition, the developer platform sets up the users (developer platform\nadministrators and application developers) who manage the solution.\n\nThis blueprint enables organizations to provide different application\ndevelopment teams (called *tenants* ) access to the platform. A tenant is a group\nof users with common ownership over a set of resources. A tenant owns one or\nmore *applications* that run on the platform as a container-based service. An\napplication on the developer platform is a bundle of source code and\nconfiguration. Each application is built and deployed by a dedicated CI/CD\npipeline. Tenants and applications are isolated from one another at run time and\nin the CI/CD pipelines. Portions of the blueprint provide automation are used by\nall tenants, and are referred to as *multi-tenant*.\n\nTo illustrate how the developer platform is used, the blueprint includes a\nsample application, called *Cymbal Bank*. Cymbal Bank is a microservices\napplication that is designed to run on GKE. The application\nis intended to simulate a highly-available application that is deployed in an\nactive-active configuration to enable disaster recovery. Cymbal Bank assumes\nthat the application is developed and operated by several independent developer\nteams.\n\nWhat's next\n-----------\n\n- Read about [architecture](/architecture/blueprints/enterprise-application-blueprint/architecture) (next document in this series)."]]