Serverless App Engine (SAE) lets you deploy and run applications from code packages or container images—without managing clusters or servers. You build and push your code; SAE handles provisioning, lifecycle management, resource optimization, monitoring, and Operations and Maintenance (O&M).
Supported applications and deployment methods
SAE supports applications written in Java, PHP, Python, Node.js, Go, and other languages. The deployment method available depends on your application type:
| Application | Deployment method | Reference |
|---|---|---|
| Spring Cloud | WAR package, JAR package, or container image | Modify service registration and discovery of applications to Nacos |
| Apache Dubbo | WAR package, JAR package, or container image | Host Dubbo applications to SAE |
| HSF | WAR package, JAR package, or container image | Host an HSF application to SAE |
| PHP | Container image or ZIP package | Deploy a PHP application by using an image and Deploy a PHP application by using a ZIP package |
| Python | Container image or ZIP package | Deploy a Python application by using an image and Deploy a Python application by using a ZIP package |
| Other languages | Container image | Deploy applications in other languages by using images |
Runtime environment by package type:
Spring Cloud or Dubbo with a WAR package: select an apache-tomcat version as the runtime environment.
Spring Cloud or Dubbo with a JAR package: select the Standard Java Application Runtime Environment.
HSF with a WAR or JAR package: select an EDAS-Container version as the runtime environment.
In addition to the SAE console and API, SAE integrates with continuous integration and continuous deployment (CI/CD) tools and IDE plug-ins for automatic deployment after code submission. Supported CI/CD tools include Jenkins and Terraform. Supported plug-ins include Maven, IntelliJ IDEA, and Eclipse.
If this is your first time deploying an application to SAE, create an application in the SAE console and push your business code to it.
Advanced deployment settings
SAE supports the following advanced settings, which you can configure when creating an application or afterward:
Startup commands
Environment variables
Hosts binding
Health checks
Log collection
Persistent storage
If you configure these settings after the application is created, the application must restart for the changes to take effect. To avoid interruptions, apply advanced settings changes during off-peak hours.
Application hosting features
After deploying an application in SAE, you can manage its entire lifecycle from the console.
| Scenario | Features |
|---|---|
| Resource management | Use namespaces to logically isolate applications, and use configuration items to store application configuration. See Manage a namespace. |
| Application deployment | Create and deploy: Create and deploy applications in SAE with advanced settings as needed. See Deploy applications. Plug-in deployment: Deploy using Maven, IntelliJ IDEA, or Eclipse plug-ins. See Plug-in deployment. CI/CD: Automate deployments with Jenkins or Terraform. See CI/CD and Terraform overview. Upgrade and rollback: Iterate on deployed applications and roll back to a previous version if an upgrade has issues. See Upgrade and roll back an application. |
| Application settings | Change the instance type, or switch the security group and vSwitch after deployment. See Change instance specifications and Change security group and vSwitch. |
| Application access | Connect deployed applications to internet resources or other VPCs by attaching a Classic Load Balancer (CLB) instance, configuring a NAT Gateway with an elastic IP address (EIP), or attaching an EIP directly to an application instance. See Application access and traffic management. |
| Application O&M | Use Webshell for basic O&M tasks such as uploading and downloading logs. Use the one-click debugging feature to diagnose instances that fail to start. See Application O&M. |
| One-click start and stop | Start or stop all applications in development, testing, and pre-release environments within the same namespace in a single action. See Perform batch operations on applications. |
| Elastic scaling | Scale an application by adjusting the number of instances to match demand. Auto scaling: For predictable traffic patterns such as periodic peaks, configure auto scaling policies to scale automatically. See Configure an auto scaling policy. Manual scaling: For sudden traffic bursts requiring immediate action, scale instances manually. See Manually scale instances. |
| Log management | Access application logs to locate and diagnose issues during O&M. See Log management. |
| Monitoring and alerting | SAE integrates with Application Real-Time Monitoring Service (ARMS) to monitor key application metrics and trigger alerts. See Application monitoring and Alert management. |
| Distributed configuration management | Centrally manage application configurations by extracting parameters and variables into configuration files uploaded to SAE. See Configuration management. |