Serverless App Engine (SAE) is suitable for multiple scenarios to help your enterprise quickly migrate applications to the cloud, handle traffic surges, start or stop application environments in a flexible manner, and reduce resource costs.
Application hosting
In production environments, you can partition your application into multiple microservices applications and use Alibaba Cloud image repositories to store the WAR package, JAR package, or Docker image of each microservices application. You only need to develop specifications and iterate each microservices application based on frameworks such as Spring Cloud or Dubbo. Then, you can use the features that are provided by SAE, such as underlying resource scheduling, microservices governance, application deployment, canary release, and monitoring and diagnostics.
Low modification costs: SAE can help you smoothly migrate applications. You can quickly migrate Spring Cloud or Dubbo applications to the cloud at low modification costs.
O&M-free: You do not need to manage or maintain the underlying infrastructure, such as IaaS, Kubernetes, microservices components, and APM components. You also do not need to use self-managed ZooKeeper, Eureka, Consul, or SkyWalking. SAE helps you reduce a large number of development and O&M costs. SAE guarantees the stability of applications that you want to commercialize.
Ease of use: SAE is a one-stop and out-of-the-box service that provides complete microservices capabilities. SAE provides the following advanced enterprise-level capabilities and features: automatic image construction, built-in canary release, traffic throttling, environment isolation, application monitoring and diagnostics, and permission management.
Auto scaling scenarios
Unexpected traffic surges may occur in various industries such as new retail, e-commerce, online education, and mutual entertainment. In such cases, you may be unable to balance the SLA of your business and resource costs. If traffic surges occur, the response latency of your systems may increase and your systems may break down. To resolve these issues, SAE provides a high-availability solution with fine-grained capacity control, elastic scalability, and throttling and bandwidth degradation. SAE helps you manage applications in case of traffic surges to reduce resource costs and ensure SLA.
Guaranteed SLA during peak hours: The elastic scalability capability of SAE and the throttling and degradation capabilities of Application High Availability Service (AHAS) can help you cope with traffic surges and prevent system breakdown.
Quick diagnosis and issue identification: SAE is seamlessly integrated with Application Real-Time Monitoring Service (ARMS) to monitor and diagnose applications in a visualized manner. You can efficiently identify slow SQL statements, slow methods, and method-call stacks. You can also analyze, troubleshoot, and resolve online issues and configure alerts.
High efficiency and low costs: SAE provides various auto scaling policies. You do not need to keep your machines active with peak workloads for a long period of time. This helps you implement auto scaling within seconds and reduce hardware costs.
Continuous integration and delivery
SAE allows you to deploy applications and jobs by using multiple services and methods, such as Apsara Devops, Jenkins, source code, Cloud Toolkit plug-in, and Container Registry. This helps you complete the DevOps process from code submission to application and job deployment. SAE replaces the traditional development mode, where deployment is complicated and iteration is slow. You can establish an efficient and continuous delivery process.
DevOps automation: SAE automates the DevOps pipeline from code update to code compiling, image building, and application deployment.
Quick deployment on the cloud: SAE supports the deployment of the Cloud Toolkit plug-in. You can deploy on-premises applications to the cloud within a few clicks. This facilitates remote debugging.
Continuous integration and continuous deployment (CI/CD): You can use SAE jobs to release computing resources immediately after the CI/CD job is completed.
