FunctionGraph provides console-based function management.
You are advised to use the latest runtime version.
Runtime | Supported Version |
|---|---|
Node.js | 6.10, 8.10, 10.16, 12.13, 14.18, 16.17, 18.15, 20.15 |
Python | 2.7, 3.6, 3.9, 3.10, 3.12 |
Java | 8, 11, 17, 21 |
Go | 1.x |
C# | .NET Core 2.1, .NET Core 3.1, .NET Core 6.0, .NET Core 8.0 |
PHP | 7.3, 8.3 |
Custom | - |
Cangjie | 1.0 |
FunctionGraph allows you to edit code inline, upload a ZIP file from Object Storage Service (OBS), or directly upload a ZIP or JAR file. Table 2 lists the code entry modes supported for each runtime.
Runtime | Editing Code Inline | Uploading a ZIP File | Uploading a JAR File | Uploading a ZIP File from OBS |
|---|---|---|---|---|
Node.js | Supported | Supported | Not supported | Supported |
Python | Supported | Supported | Not supported | Supported |
Java | Not supported | Supported | Supported | Supported |
Go | Not supported | Supported | Not supported | Supported |
C# | Not supported | Supported | Not supported | Supported |
PHP | Supported | Supported | Not supported | Supported |
Custom | Supported | Supported | Not supported | Supported |
Cangjie | Not supported. | Supported | Not supported | Supported |
FunctionGraph supports multiple trigger types, such as Simple Message Notification (SMN), API Gateway (APIG), and OBS trigger types. Table 3 lists the supported trigger types and the function invocation mode of each trigger type.
Trigger | Function Invocation Mode |
|---|---|
SMN trigger | Asynchronous invocation |
APIG trigger | Synchronous invocation |
OBS trigger | Asynchronous invocation |
Data Ingestion Service (DIS) trigger | Asynchronous invocation |
Timer trigger | Asynchronous invocation |
Log Tank Service (LTS) trigger | Asynchronous invocation |
Cloud Trace Service (CTS) trigger | Asynchronous invocation |
Kafka trigger | Asynchronous invocation |
FunctionGraph graphically displays function monitoring metrics and collects function running logs, enabling you to view function statuses, and locate problems by querying logs.
For details on how to query logs, see Querying Logs.
For details on how to view function metrics, see Viewing Function Metrics.
For details about tenant-level monitoring information, see Dashboard.
The initializer interface is introduced to:
You can set Function Type to HTTP Function on the function creation page. HTTP functions are designed to optimize web services. You can send HTTP requests to URLs to trigger function execution. HTTP functions support API Gateway (APIG) triggers only.
You can directly package and upload container images. The images are loaded and started by the platform and can be called in a similar way as HTTP functions. Unlike the previous code upload mode, you can use a custom code package, which is flexible and reduces migration costs.