Release Notes
Security Announcement
Announcements
Business types provided | Supported capabilities | Mainly address problems | Common scenario examples |
| Provide rich features such as dynamic and static CDN acceleration, Web protection, Bot management, edge functions, and media services for websites/apps/businesses accessed via domain names. | Slow access speed in business: Users experience slow access speeds when accessing through different regions and operators, and are prone to buffering and access failures. Suffer from network attacks: There exist various types of network attacks in currently connected business, such as risk of being stolen, vulnerability attack, CC attack and Bot crawler. Poor server performance: The server bandwidth resource and performance of the site are limited. When a large number of users access it centrally, it will cause the origin server to be unable to host, resulting in users' access being unavailable. | For example: portal website, game download, popular video on demand, social forum, transaction/payment/login API, OTA upgrade and other scenarios. |
| Provide L4 proxy acceleration for TCP/UDP requests and support providing exclusive DDoS protection. | Provide security acceleration for businesses that cannot be accessed via domain names, such as those based on Layer 4 forwarding. | For example: global office application acceleration, global game server co-location, TRTC connection and other business scenarios. |
By importing Git repositories, using templates, or directly uploading, users can quickly build and deploy static sites and serverless applications. Additionally, with the capability of Edge functions, efficient content delivery and dynamic functionality expansion can be achieved to support fast access for global users. | Deployment process is cumbersome: The cycle from code writing to deployment and launch is long, making it difficult to ensure rapid iteration of projects, allowing companies to quickly respond to market demands. Slow page access speed on sites: Users find it hard to have a smooth experience during access, resulting in poor website performance. Complex server deployment and high server-side development costs: It requires self-configuration and management of servers and other infrastructure, making it impossible to directly write ultra-low-latency server logic at edge nodes. | For example: Personal blog, brand official website, event promotion page, AI integration application, documentation site, etc. | |
Was this page helpful?
You can also Contact sales or Submit a Ticket for help.
Help us improve! Rate your documentation experience in 5 mins.
Feedback