Volcano Engine Function as a Service
Category | Feature | Description |
Application | An application is a deployment unit for complete business scenarios. It orchestrates functions and dependent resources and supports quick template deployment. | |
| Creates, deploys, updates, and deletes applications. Functions and resources under an application are managed in a centralized manner. | |
| Starts or stops applications as needed and flexibly controls running status and resource usage. | |
| Automatically build images and deploy applications after code repositories are associated to achieve continuous delivery. | |
Function | Creates, deploys, updates, and deletes functions. Functions can be deployed through code packages and images. | |
| Configures the instance memory size, maximum number of instances, concurrency per instance, execution timeout, VPC network, storage, environment variable, and more. | |
| Supports various triggers such as Timer, APIG, TOS, Kafka, RocketMQ, and BMQ to meet the requirements of different event-triggered scenarios. | |
| Automatically scales in or out based on request volume and provisions instances to reduce cold-start latency. | |
| Releases code and configurations based on version snapshots. Supports full release and canary release. Monitors the release process and manages releases and version records. | |
| Provides metric monitoring, persistent logging (TLS), real-time instance logs, instance WebShell, and online testing to support function observability and debugging. | |
| Collects statistics on resource allocation for accounts and individual functions. Maximum function resources = Instance memory specification × Maximum number of instances. This facilitates appropriate resource allocation and cost control. | |
|
| |
Cloud sandboxes | Creates and manages sandbox applications, which provide runtime templates and configuration for sandbox instances. | |
| Creates, suspends, resumes, and deletes sandbox instances and supports file system snapshots. | |
| Manages the images required for sandbox execution and specifies custom sandbox environments. | |
| Pre‑creates and maintains a certain number of sandbox instances to reduce cold‑start latency. |