[[["易于理解","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)：2025-07-31。"],[],[],null,["# Learning Path: Scalable applications - Overview\n===============================================\n\nThis set of tutorials is for IT administrators and Operators that want\nto learn how to deploy, run, and manage modern application environments that run\non Google Kubernetes Engine (GKE) Enterprise edition.\n\nIn this set of tutorials, you learn by doing. You start by deploying a sample\nmicroservices-based application named Cymbal Bank to a GKE\ncluster. Cymbal Bank uses Python and Java to run the various services, and\nincludes a PostgreSQL backend. You don't need experience with these languages or\ndatabase platform to complete the series of tutorials, as Cymbal Bank is just an\nexample application to show how GKE Enterprise can support the\nneeds of your business. Each tutorial then builds on this sample application to\nshow how a real production environment might look as you use different\nGoogle Cloud products and services to fit your business needs and\ngoals.\n\nAs you progress through this set of tutorials, you explore the following key\nlearning areas:\n\n- **Modern application foundations**: Deploy a single Google Kubernetes Engine cluster that runs a microservices-based application.\n- **Monitoring and SLOs**: Use Prometheus to monitor the performance and health of your applications, and use Cloud Service Mesh to set and track SLOs.\n- **Autoscale and load balance**: Scale your cluster to meet application demand with GKE Autopilot, and use horizontal Pod autoscaling for a database tier.\n- **Simulate and test failovers**: Verify that your highly available and geographically distributed deployment can failover to maintain access for customers.\n- **Centralize change management**: Minimize configuration drift and apply consistent changes with Config Sync.\n\nThe tutorials are designed for you to complete in order. Each tutorial builds on\nthe previous tutorial as you create a sample application infrastructure that you\ncan monitor and autoscale. As you progress through the set of tutorials, you\nlearn new skills and use additional Google Cloud products and services.\nThe goal is that you learn all of the core components that are needed to feel\nmore comfortable running scalable applications in your own environment.\n\nYour journey\n------------\n\nFor this set of tutorials, you play the role of the platform lead at Cymbal\nBank. Cymbal Bank started as a small business for payment processing on two\nservers almost ten years ago. Since then, it has grown into a successful\ncommercial bank with thousands of employees and a growing engineering\norganization. Cymbal Bank now wants to expand its business further.\n\nThroughout this period, you and your team have found yourself spending more time\nand money on maintaining infrastructure than on creating new business value. You\nhave decades of cumulative experience invested in your existing stack; however,\nyou know it's not the right technology to meet the scale of global deployment\nthat the bank needs as it expands.\n\nYou've adopted GKE Enterprise to modernize your application and\nmigrate successfully to Google Cloud to achieve your expansion goals.\n\nCosts\n-----\n\nEnabling GKE Enterprise and deploying the Cymbal Bank sample\napplication for this series of tutorials means that you incur per-cluster\ncharges for GKE Enterprise on Google Cloud as listed on our\n[Pricing page](/kubernetes-engine/pricing)\nuntil you disable GKE Enterprise or delete the project.\n\nYou are also responsible for other Google Cloud costs incurred while running the\nCymbal Bank sample application, such as charges for Compute Engine VMs and\nload balancers.\n\nBefore you begin\n----------------\n\nBefore reading this page, ensure that you're familiar with\n[Kubernetes basics](https://kubernetes.io/docs/tutorials/kubernetes-basics/),\nsuch as clusters.\nYou don't need to be familiar with Google Kubernetes Engine (GKE) Enterprise edition or Terraform to\nfollow these tutorials.\n\nEach tutorial outlines specific prerequisites, such as needing a\nGoogle Cloud billing account and project or IAM roles.\n\nPlanning considerations\n-----------------------\n\nWhen you plan a production GKE Enterprise environment, there are\na number of planning considerations to keep in mind. These considerations\ninclude available networking options, your cluster management mode, and cluster\navailability.\n\nIn this set of tutorials, some of these considerations are simplified so that\nyou can focus on learning about key GKE Enterprise features and\nservices. Because of this, these tutorials don't provide a complete\nproduction-ready environment, but rather give you the building blocks you need\nto learn how to deploy and run your own workloads. After you complete this\nset of tutorials, we recommend you review\n[Scalable apps - Production considerations](/kubernetes-engine/enterprise/docs/learn/scalable-apps-considerations).\n\nWhat's next\n-----------\n\nGet started by completing the\n[first tutorial to a deploy a single GKE cluster](/kubernetes-engine/enterprise/docs/learn/scalable-apps-basic-deployment)\nthat runs a microservices-based application."]]
