1. Business Background Once an enterprise reaches a certain scale, relying entirely on public cloud infrastructure makes IT costs very high. The cost of purchasing physical machines can be amortized over the next 3 to 5 years, and afterwards the machines are not scrapped; instead they continue to serve beyond their planned lifespan.

1. HPA VS KEDA HPA also provides: Elasticity based on custom metrics Scale to Zero Compared with KEDA, these are no longer disadvantages. The real difference is that HPA can only scale using monitoring data, whereas KEDA can scale using many more data sources — queue messages, databases, Redis, and so on, including monitoring data as well.

1. Introduction to WebAssembly Cross-platform: it can run on any platform that supports WebAssembly, including web browsers, servers, and mobile devices High performance: it uses a compact binary format that can be loaded and parsed quickly in the browser, improving application performance Security: it uses a sandbox model that isolates the code running inside it, protecting the system from malicious code

1. Container-Based Serverless Cannot Support the Next Generation of Applications As the figure above shows, we are going through a change in runtime form. From bare metal to virtual machines, applications are no longer limited by the number of local servers or the stability of the data center, and gain better elasticity and availability.

1. A Constrained Build Environment Cannot Meet Build Requirements Tekton is a CICD engine based on a Kubernetes cluster, and it is more cloud-native than Jenkins. In plain terms, that means it is easier to develop plugins for, easier to scale, easier to observe, and more fun. Because code can only be stored on the company intranet, the build cluster can only be deployed on the office intranet.