tencent cloud

Tencent Cloud EdgeOne

Release Notes and Announcements
Release Notes
Security Announcement
Announcements
Product Introduction
Overview
Strengths
Use Cases
Comparison Between EdgeOne and CDN Products
Use Limits
Purchase Guide
Description of Trial Plan Experience Benefits
Free Plan Guide
Billing Overview
Billing Items
Subscriptions
Renewals
Instructions for overdue and refunds
Comparison of EdgeOne Plans
About "clean traffic" billing instructions
DDoS Protection Capacity Description
Getting Started
Choose business scenario
Quick access to website security acceleration
Quick deploying a website with Pages
Domain Service&Origin Configuration
Domain Service
HTTPS Certificate
Origin Configuration
Site Acceleration
Overview
Access Control
Smart Acceleration
Cache Configuration
File Optimization
Network Optimization
URL Rewrite
Modifying Header
Modify the response content
Rule Engine
Image&Video Processing
Speed limit for single connection download
DDoS & Web Protection
Overview
DDoS Protection
Web Protection
Bot Management
API Discovery(Beta)
Edge Functions
Overview
Getting Started
Operation Guide
Runtime APIs
Sample Functions
Best Practices
Pages
L4 Proxy
Overview
Creating an L4 Proxy Instance
Modifying an L4 Proxy Instance
Disabling or Deleting an L4 Proxy Instance
Batch Configuring Forwarding Rules
Obtaining Real Client IPs
Data Analysis&Log Service
Log Service
Data Analysis
Alarm Service
Site and Billing Management
Billing Management
Site Management
Version Management
General Policy
General Reference
Configuration Syntax
Request and Response Actions
Country/region and Corresponding Codes
Terraform
Overview
Installing and Configuring Terraform
Practical Tutorial
EdgeOne Skill User Guide
Automatic Warm-up/Cache Purge
Resource Abuse/hotlinking Protection Practical
HTTPS Related Practices
Acceleration Optimization
Scheduling Traffic
Data Analysis and Alerting
Log Platform Integration Practices
Configuring Origin Servers for Cloud Object Storage (Such As COS)
CORS Response Configuration
API Documentation
History
Introduction
API Category
Making API Requests
Site APIs
Acceleration Domain Management APIs
Site Acceleration Configuration APIs
Edge Function APIs
Alias Domain APIs
Security Configuration APIs
Layer 4 Application Proxy APIs
Content Management APIs
Data Analysis APIs
Log Service APIs
Billing APIs
Certificate APIs
Origin Protection APIs
Load Balancing APIs
Diagnostic Tool APIs
Custom Response Page APIs
API Security APIs
DNS Record APIs
Content Identifier APIs
Legacy APIs
Ownership APIs
Image and Video Processing APIs
Multi-Channel Security Gateway APIs
Version Management APIs
Data Types
Error Codes
FAQs
Product Features FAQs
DNS Record FAQs
Domain Configuration FAQs
Site Acceleration FAQs
Data and Log FAQs
Security Protection-related Queries
Origin Configuration FAQs
Troubleshooting
Reference for Abnormal Status Codes
Troubleshooting Guide for EdgeOne 4XX/5XX Status Codes
520/524 Status Code Troubleshooting Guide
521/522 Status Code Troubleshooting Guide
Tool Guide
Agreements
Service Level Agreement
Origin Protection Enablement Conditions of Use
TEO Policy
Privacy Policy
Data Processing And Security Agreement
Contact Us
Glossary

Overview

PDF
Focus Mode
Font Size
Last updated: 2024-07-16 10:17:02
Tencent Cloud Edge Functions provides a serverless code execution environment for the edge nodes of Tencent Cloud EdgeOne. This way, you can focus on writing business function code and configuring triggering rules, without the need to configure or manage infrastructure such as servers. The written code can be elastically and securely executed on the edge nodes that are closest to users.


How It Works


You can develop JavaScript functions and deploy them to the edge nodes of Tencent Cloud EdgeOne.
1. If a client request does not hit the configured function triggering rule, the request is handled in the following process:
(1) The client request is sent to the gateway of an edge node of Tencent Cloud EdgeOne. > (2) The cache of the node responds if the requested content already exists in the cache. > (3) The origin server responds if the requested content does not exist in the cache.
2. If a client request hits the configured function triggering rule, the request is handled in one of the following processes:
(1) The client request is sent to the gateway of an edge node of Tencent Cloud EdgeOne. > (4) Edge Functions receives and executes the JavaScript code. > (5) Subrequests access the cache. > (3) The origin server responds if the requested content does not exist in the cache.
(1) The client request is sent to the gateway of an edge node of Tencent Cloud EdgeOne. > (4) Edge Functions receives and executes the JavaScript code. > (6) Subrequests access the public network service.

Benefits

Distributed Deployment

Tencent Cloud EdgeOne supports more than 3,200 edge nodes. Edge Functions is deployed on edge nodes in distributed mode.

Ultra-low Latency

Client requests are automatically scheduled to the edge nodes that are closest to users. If triggering rules are hit, edge functions are triggered to process the requests and return results to the client. This helps significantly reduce the client access latency.

Elastic Scaling

Edge Functions schedules requests to edge nodes that are allocated sufficient computing resources based on the proximity of the user when spikes occur in client requests.

Serverless Architecture

The serverless architecture of Edge Functions eliminates the need to focus on the maintenance of the memory, CPU, and network of servers and other infrastructure resources. You can focus on the development of business code.

Use Cases



Use Limits

Content
Limit
Note
Number of Functions per Site
100 functions
A single site supports up to 100 edge functions.
Number of Trigger Rules per Site
200 rules
A single site supports up to 200 trigger rules for functions.
Function Name Length
30 characters
2 to 30 characters, up to 30 characters.
Code Package Size
5 MB
The maximum size for a single function code package is 5 MB.
Request Body Size
1 MB
Client requests can carry a body up to 1 MB.
CPU Time
200 ms
CPU time slice allocated for single function execution, excluding I/O waiting time.
Programming Language
JavaScript
Currently only JavaScript is supported.
Number of Console Invocations
20 times
Each function is allowed to call the console method up to 20 times. Beyond 20 times, print operations will no longer be executed.
Number of Loop Executions
100,000 times
In the function, the for, for in, for of, while, do while loops are limited to execute no more than 100,000 times.


Help and Support

Was this page helpful?

Help us improve! Rate your documentation experience in 5 mins.

Feedback