SCF allows you to deploy container images as functions. This document describes the background, principles, development, log printing, cold start optimization, billing, and use limits of image deployment functions.

Background

SCF is a FaaS service based on the cloud native architecture from the very beginning of design. After adding support for deploying container images as functions at the runtime layer, its entire service form has evolved towards a containerized ecosystem. On the one hand, it solves the environment dependency problem in function runtime and gives you more freedom to customize. On the other hand, this service form enables you to cross the technical thresholds, such as Kubernetes cluster management, security maintenance, and troubleshooting, and sinks auto scaling, availability, and other needs to the computing platform, further unleashing the capabilities of cloud computing.

How It Works

Before developing specific function logic, you need to determine the function type. SCF provides event functions and web functions.

During function instance initialization, SCF gets the temporary username and password as the access credentials to pull the image. After successfully pulling the image, SCF starts the HTTP server defined by you based on the defined Command start command, Args parameter, and port (which is fixed at 9000). Finally, the HTTP server receives all entry requests of SCF, including those from your event and web function invocations.

How a function works is as shown below:

Developing Function Deployed Based on Image

Building HTTP server

For a function deployed based on an image, you need to build an HTTP server and configure it as follows:

• It should listen on 0.0.0.0:9000 or *:9000.
• It should be started within 30 seconds.

If the above step is not completed, health check may time out, and the following error may be reported:

The request timed out in 30000ms.Please confirm your http server have enabled listening on port 9000.

Function input parameters

• event: POST request body (HTTP body)
  The request body contains the event data. For its structure, please see Trigger Event Message Structure Summary.

• context: request header (HTTP header)

  • Common parameters: parameters used to identify the user and API signature, which must be carried in each request.
  • Use X-Scf-Request-Id to get the current request ID.

    Note

    Both event and web functions should contain common headers.

    The common request headers are generated by SCF, which mainly contain permissions and basic function information.

    The input parameters are as detailed below:

    Header Field	Description
    X-Scf-Request-Id	Current request ID
    X-Scf-Memory	Maximum memory that can be used during function instance execution
    X-Scf-Timeout	Timeout period for function execution
    X-Scf-Version	Function version
    X-Scf-Name	Function name
    X-Scf-Namespace	Function namespace
    X-Scf-Region	Function region
    X-Scf-Appid	`Appid` of function owner
    X-Scf-Uin	`Uin` of function owner
    X-Scf-Session-Token	Temporary `SESSION TOKEN`
    X-Scf-Secret-Id	Temporary `SECRET ID`
    X-Scf-Secret-Key	Temporary `SECRET KEY`
    X-Scf-Trigger-Src	Timer (if a timer trigger is used)

Built-in environment variables

Environment variables built in the container in custom image-based deployment are different from those in code package-based deployment. You can import them as needed.

Function invocation

• For event functions, you need to listen on the fixed path /event-invoke to receive function invocation requests.
• For web functions, you don't need to listen on a specified path; instead, API Gateway uses layer-7 reverse proxy to pass through the request path.

Function log printing

SCF collects standard output logs such as stdout and stderr generated in the container in a non-intrusive manner and reports them to the log module. After invoking a function, you can view the aggregated logs in the console.

Cold Start Optimization

As file layers such as basic environment and system dependency are added to the image, compared with code package-based function deployment where files are completely built-in, image-based function deployment requires extra file download and image decompression time. To further reduce the cold start time, we recommend you use the following practices:

• Create an image repository and a function in the same region, so that the image can be pulled over VPC when the function triggers image pull, which makes the pull faster and more stable.
• The image should be as small as possible, that is, it should contain only the necessary basic environment and execution dependencies without any unnecessary files.
• Use provisioned concurrency when deploying an image to start a function instance in advance and thus reduce the cold start time and optimize the user experience. For more information, please see Provisioned Concurrency.

Billing Description

The billable items of image-based functions are the same as those of code package-based functions. For more information on billing, please see Billing Mode.

Use Limits

Image size

Currently, only images below 1 GiB in size are supported. We recommend you select an appropriate function instance execution memory based on the image size.

Image repository access

• Currently, only the TCR Enterprise Edition and Personal Edition are supported. For more information, please see Tencent Container Registry.
  • For more information on the TCR Enterprise Edition, please see Basic Image Repository Operations.
  • For more information on the TCR Personal Edition, please see Getting Started.
• Currently, only images in a private image repository in the same region can be read.

Permission to read/write file in container

• /tmp is readable and writable by default. We recommend you select /tmp when outputting a file.
• Avoid using other users' files with restricted access or execution.
• The storage space of the writable layer in the container is 512 MB.

Image build client limits

The client should meet one of the following requirements:

• Docker Image Manifest v2, Schema 2 (Docker should be on v1.10 or above)
• Open Container Initiative (OCI) Specifications (v1.0.0 or above)