Feature | Description | Region | Related document |
You can enable a single instance to process multiple concurrent requests for asynchronous tasks. | The feature of enabling a single instance to process multiple concurrent requests is added for synchronous tasks. After you enable this feature, a single instance can process multiple concurrent requests. | All | |
The MQ consumer function template is added. | The Message Queue (MQ) consumer function template is added under the microservices app category, which allows you to deploy and start a data processing service with a few clicks to synchronize the data from MQ to Cloud Search (ES). | All | |
Asynchronous tasks support custom startup commands. | You can specify a custom startup command when you submit an asynchronous task each time to meet the requirements of diverse task execution scenarios. | All | |
Projects and tags can be configured for functions. | You can group and manage function resources by project and tag. In this way, you can perform operations on resources in groups such as Identity and Access Management (IAM) authorization and bill splitting. | All | |
Scheduled scaling policies can be configured for functions. | When a function exhibits obvious periodic patterns or predictable traffic spikes, you can configure scheduled policies based on business characteristics to implement scheduled scaling of instances. This improves instance utilization and addresses resource waste. | All | |
The application center provides the Mirror Maker data synchronization application. | [Beta - apply for trial] The application center provides the volcano-mirror-maker application template, which hosts the Mirror Maker 2.0 microservices app and supports data synchronization between Kafka clusters. | All |
Feature | Description | Region | Related document |
Microservices app hosting | veFaaS has launched the microservices app hosting feature for hosting microservices apps in the CPU always allocated mode. You can directly host container applications without the need to integrate microservices apps with triggers. | All |
Feature | Description | Region | Related document |
The Node.js runtime supports online dependency installation. | The Node.js runtime supports online installation of dependencies, which simplifies the procedure and prevents errors that may occur during local installation, packaging, and upload of dependencies. | All | |
The native Python runtime is added. | Native Python 3.8, 3.9, and 3.12 runtimes are added, which enable you to develop web apps by using native Python HTTP frameworks without the need to install third-party interpreters. | All | |
A code package can be uploaded when a function is being created. | When you create a function, you can upload a ZIP package from your on-premises device or through a TOS bucket, which simplifies the procedure. | All |
Feature | Description | Region | Related document |
The asynchronous task feature supports non-webserver mode. | The non-webserver mode is added for the asynchronous task feature, which allows you to execute scripts by using tasks without the need to implement an HTTP server. The process will automatically terminate if the execution is complete or times out. | All | |
You can specify custom startup commands and ports for serverless application hosting. | Custom startup commands and ports can be configured for serverless application hosting, which eliminates the need to write the run.sh startup script and helps you smoothly migrate native web framework applications. | All | |
The Python runtime supports online dependency installation. | The Python runtime supports online installation of dependencies, which simplifies the procedure and prevents errors that may occur during local installation, packaging, and upload of dependencies. | All | |
The native runtime is officially available. | The native runtime is a custom runtime environment provided by veFaaS, which can be deployed through a code package and a container image. You can create a dedicated function execution environment by using the native runtime. | All | |
The asynchronous task feature is officially available. | The asynchronous execution mode can be used to respond to invocation events and track and monitor task status. This feature is suitable for long-running or compute-intensive tasks, which can address issues such as continuous occupation of caller resources during synchronous invocation and meet the requirements for high stability of traces. | All | |
The serverless application center is officially available. | This feature aggregates function instances, triggers, and other dependent cloud resources, which helps you deploy serverless applications with a few clicks and achieves the full-lifecycle management of applications. | All | |
The Express.js web service application template is added. | This feature helps you deploy Express.js web services with a few clicks. | All |
Feature | Description | Region | Related document |
Prepaid resource packages are added. | veFaaS has launched prepaid resource packages, which can be used to offset different billing items. This billing method is more cost-efficient than pay-as-you-go. | All | |
GPU functions support reserved instances and billing. | Static reserved instances can be configured for GPU functions. As a result, reserved instances can be configured for both CPU functions and GPU functions. | All | |
A function can be configured to access the public network. | After VPC access is enabled for a function, users can specify how the function accesses the public network. | All | |
The TLS trigger is added. | Torch Log Service (TLS) is added as one of the event sources for veFaaS, which enables you to write functions to perform extract, transform, and load (ETL) processing on massive logs. | All |
Feature | Description | Region | Related document |
The serverless application center is added. | [Beta] This feature aggregates function instances, triggers, and other dependent cloud resources, which helps you deploy serverless applications with a few clicks and achieves the full-lifecycle management of applications. | All | |
Static reserved instance support for CPU functions | Configuring static reserved instances effectively prevents request latency caused by cold starts of elastic instances during peaks of function invocation. warning You will be charged for reserved instances. Regardless of whether a request is executed, the memory usage fees of reserved instances will be continuously generated until the instances are released. | All | |
Outbound Internet traffic is billed on a pay-as-you-go basis. | veFaaS starts to charge you for outbound Internet traffic routed through the default network interface card (NIC). The traffic is billed on a pay-as-you-go basis. Make sure that your account balance is sufficient to prevent your business from being disrupted. | All | |
Capacity FileNAS can be mounted. | You can configure Capacity FileNAS for functions, which provides more options to meet the requirements of different business scenarios. | All |
Feature | Description | Region | Related document |
TOS can be mounted. | You can configure Torch Object Storage (TOS) for a function. You can specify a mapping relationship between a bucket subdirectory and the local directory of the function to grant the read and write permissions on the bucket subdirectory to the function. This solution overcomes the limitations of local disk space, which achieves persistent data storage and sharing among multiple functions. | All | |
The logic for retrieving asynchronous task logs is optimized. | You can identify the complete logs for each task by using the instance name and the start and end times of the task. In this case, the request ID is not required. | All |