Volcano Engine Function as a Service
Comparison item | Task |
Comparison item | Task | |||
Application scenarios | Write programs by using the interface defined by veFaaS. |
|
| Respond to asynchronous invocation requests through the task mode, where the program exits after execution. The status of each task phase can be tracked and persisted, which provides rich task control and observability capabilities. |
Deployment method | Code package |
|
|
|
CPU allocation mode | CPU is allocated only during request processing | CPU is allocated only during request processing | CPU is always allocated | CPU is allocated only during request processing |
GPU instance support | Not supported | Supported when using container imagesner images | Supported when using container images | Supported when using container images |
Cold start | Fatest. The cold start is the fastest because the code package does not include the runtime. | Deployment through a code package is faster than that through a container image. | Deployment through a code package is faster than that through a container image. | Deployment through a code package is faster than that through a container image. |
Code package size and format | The uncompressed code package is a .zip file with a size of up to 256 MiB. | | | |
Image size and format | | | | |
Runtime environment | Python, Golang, and Node.js | Native Python and Native | Native | Native |
Traffic integration method | Triggers | Triggers | Triggers are not supported. | Triggers |