Description Of Billing Capability Items
Last updated:2025-11-22 10:05:18
Cloud Database
Database Rollback
Feature definition
Support users to restore the database to the state at a specified time point, enabling quick data rollback to the healthy status before misoperations, exceptions, or disasters.
Why It Is Needed to Roll Back a Feature
1. Misoperation Recovery: The Ultimate Assurance for Data Security
During development or maintenance, scenarios like accidentally deleted tables, incorrect data updates, or mis-executed scripts occur frequently. Traditional backup restoration takes up to several hours, while the rollback feature can locate the time point before the misoperation in seconds, quickly restore data, and minimize business interruption loss.
Typical scenario: During an e-commerce promotion, the order table was accidentally cleared. Roll back to the state 10 minutes ago within 5 minutes to avoid data loss of tens of millions of transactions.
2. Security Protection: Protection Shield Against Attacks and Abnormalities
When facing data corruption caused by SQL injection, ransomware attacks, or program bugs, traditional solutions require manual troubleshooting of the contamination source and row-by-row fixes, which is inefficient and high-risk.
"Rollback" can skip directly the contaminated time period and restore to security status, drastically shortening the failure recovery period.
3. Compliance audit: Meet regulatory requirements
The finance, health care and other industries need to meet strict data retention and trace requirements.
The "rollback" feature provides data version management accurate to the minute, coping easily with regulatory review and avoiding legal risk.
Exclusive (Exclusive Database Access)
Feature definition
Two levels of resource isolation schemes are provided: dedicated sharing (a small number of users share the same database instance) and independent instance (an entirely independent dedicated resource pool), ensuring business operations are not disrupted by a large number of requests from other users, achieving resource isolation and performance guarantee as needed.
Why It Is Needed to Have an Exclusive Feature
1. Slow log optimization: Eliminate performance bottlenecks
In the default share database environment, slow queries from other tenants' occupy large system resources, leading to performance degradation for all users.
The "Exclusive" feature ensures user's query performance is not impacted by others through resource isolation, while allowing database configuration optimization based on own business characteristics.
Typical scenario: During major promotions on e-commerce platforms, database queries surge. In a shared environment, query time increases from milliseconds to seconds, seriously affecting user experience. In an exclusive environment, even in the face of traffic peaks, query performance remains stable, and order processing latency is controlled within the acceptable range.
2. Performance guarantee: Eliminate resource contention
In a shared database environment, multiple users' concurrent requests can cause CPU and I/O resource competition, leading to a spike in business response delay (for example, from 10ms to over 500ms).
Exclusive mode allocates a dedicated resource pool for users, guaranteeing core business stability and low latency (such as payment, real-time transactions), with distinct user experience enhancement.
3. Business stability: Key business assurance
Financial transactions, medical imaging, and other scenarios with extremely high stability requirements where any performance fluctuations may result in significant loss.
The "exclusive" feature uses physical isolation to eliminate multi-tenant interference, ensuring over 99.99% SLA (service availability), enabling business operations to run like an "exclusive expressway".
Serverless Cloud Function (SCF)
Timeout Period/Memory Configuration (Resource Extension Configuration)
Feature definition
Users are allowed to customize the running time cap and memory allocation of cloud functions according to business needs, breaking through default resource limitations, supporting more complex and compute-intensive task processing to enhance application performance and user experience.
Why It Is Needed "Timeout/Memory Configuration" Feature
1. Complex task processing: Break through default limits
Default SCF configuration (3-second timeout, 256MB Memory) cannot meet the requirements of data processing, AI inference and complex calculations.
The "Timeout/Memory Configuration" feature enables extending the running time up to 900s and memory to several GB, allowing SCF to handle more extensive business scenarios.
Typical scenario: Video transcoding service needs to process large video files. By configuring a longer timeout period (e.g., 600s) and larger memory (e.g., 2GB), it ensures smooth completion of complex transcoding tasks without having to worry about interruptions caused by resource insufficiency.
2. Performance optimization: Accelerate business response
SCF performance is directly proportional to allocated memory. Insufficient memory can cause slow computation and affect user experience.
The "Timeout/Instance Memory Configuration" feature significantly improves function execution speed, reduces waiting time, and enhances business response efficiency by adding memory allocation.
Typical scenario: Ecommerce platform's product recommendation algorithm needs to calculate user preferences in real-time and return the result. By upgrading memory from default 128MB to 1GB, calculation time is shortened from original 3 seconds to 300ms, drastically improving user browsing experience.
3. Cost-effective balance: Flexible resource allocation
Different business scenarios have varying needs for computational resources. Unified configuration may lead to resource waste or shortage.
"Timeout/Memory Configuration" feature support allows adjusting resource configuration as needed to achieve the best balance between cost and performance, improving resource utilization efficiency.
Typical scenario: Business data analysis tasks execute every midnight with low real-time requirement but need to process large volumes of data. By configuring an extended timeout period (such as 10 minutes) and moderate memory (such as 512MB), it ensures task completion while avoiding additional cost caused by excessive configuration.
Connecting Tencent Cloud VPC (VPC Network Connection)
Feature definition
Allow SCF to connect to designated Tencent Cloud VPC (Virtual Private Cloud) network environments, enabling functions to securely access private resources within the VPC, such as databases, cache, and internal APIs. Meanwhile, hybrid private and public network access capability can be achieved by configuring the gateway.
Why It Is Needed to "Connect Tencent Cloud VPC" Feature
When your cloud function needs to access resources deployed in Tencent Cloud VPC, this feature must be enabled.
Typical use cases:
Access databases, cache, or Message Queue only accessible over a private network
Call in-house APIs or microservices
Access local data center resources via dedicated line
Strict cybersecurity requirements, avoid exposing resources to public networks
Fixed Public Outbound IP
Feature definition
Provide a fixed public outbound IP for SCF with public network access enabled. This IP remains consistent across multiple functions in the same environment, ensuring requests from SCF always originate from the same identifiable source IP.
Why It Is Needed "Static IP" Feature
When your SCF needs to call a third-party service with allowlist restriction, this feature must be enabled.
Typical use cases:
WeChat Pay, WeCom and other services that require IP allowlist configuration
Banks, financial institutions' API Gateway (usually requiring fixed source IP)
Enterprise-level API for partners (access control based on IP)
Cloud Management
Grayscale release
Feature definition
Allow the cloud hosting service to manually control traffic flow to the new version by ratio or by condition after releasing a new version, so that the new version's capacity can be gradually rolled out.
Why It Is Needed "Full-Link Grayscale Release" Feature
When you expect a business launch to proceed gradually in batches, you can use this feature.
Typical use cases:
Provide new capabilities to a small batch of users in advance
Perform user AB testing
Designated users trial new capabilities in advance
Connecting Tencent Cloud VPC (VPC Network Connection)
Feature definition
Allow cloud hosting service to connect to designated Tencent Cloud VPC (Virtual Private Cloud) network environments, enabling running services to securely access private resources within the VPC, such as databases, cache, and internal APIs. Meanwhile, hybrid private and public network access capability can be achieved by configuring the gateway.
Why It Is Needed to "Connect Tencent Cloud VPC" Feature
When your cloud hosting service needs to access resources deployed in Tencent Cloud VPC, this feature must be enabled.
Typical use cases:
Access databases, cache, or Message Queue only accessible over a private network
Call in-house APIs or microservices
Access local data center resources via dedicated line
Strict cybersecurity requirements, avoid exposing resources to public networks
Fixed Public Outbound IP
Feature definition
Provide a fixed public outbound IP for cloud hosting service. This IP is provided at the environment dimension, and all cloud hosting services in the same environment use this IP as their public outbound IP.
Why It Is Needed "Static IP" Feature
When your cloud hosting service needs to call a third-party service with whitelist restrictions, this feature must be enabled.
Typical use cases:
WeChat Pay, WeCom and other services that require IP allowlist configuration
Banks, financial institutions' API Gateway (usually requiring fixed source IP)
Enterprise-level API for partners (access control based on IP)
Access Control
Traffic Throttling and Request Frequency Control
Feature definition
Support setting call frequency limits for SCF, cloud hosting service, or cloud access path settings, enabling granular control from both resource and path perspectives, effectively preventing resource abuse and abnormal calls, ensuring system stability and cost control.
Why It Is Needed to Enable Traffic Throttling Feature
1. Backend service scenario: Backend throttling
Third-party access security: Defend against DDoS attacks
Businesses face the risk of malicious attacks or misuse when opening APIs to partners, possibly resulting in service interruption.
The "Traffic Throttling" feature allows setting differentiated call quotas for accessing parties. Once abnormal traffic is detected, throttling is triggered immediately to ensure core business not affected.
Typical scenario: When a payment platform faces a DDoS attack, the throttling mechanism automatically identifies and blocks abnormal traffic while ensuring normal merchant transaction requests remain unaffected, maintaining business continuity.
Resource optimization allocation: Partner hierarchical management
Different levels of partners require differentiated API call permission and resource allocation.
"Traffic throttling and frequency limiting" feature supports setting different QPS caps based on partner identity to allocate resources reasonably and provide flexible support for business models.
Typical scenario: The map service platform provides differentiated API invocation limits for corporate customers with different payment levels. Senior members enjoy higher call frequency, while basic members are subject to stricter limits, achieving commercialized service tiering.
2. End user scenario: C-end user security gateway
WAF firewall mechanism: Comprehensive security protection
Websites and applications face various network attack threats, such as SQL injection, XSS attack and malicious bots.
The "Traffic throttling and frequency limiting" feature integrates WAF firewall capacity, supports IP allowlist/blocklist, Hotlink protection, and access frequency limit configuration, building a multi-level security protection system.
Typical scenario: Content platforms use Hotlink protection to prevent resources from being illegally referred, with concurrent configuration of IP blocklist blocking known malicious sources, effectively protecting platform content assets and service stability.
Abnormal behavior control: Prevent resource abuse
End users' abnormal operations (such as frequent refresh and script automated operations) may consume a large amount of system resources, impacting overall service quality.
The "Traffic Throttling" feature can perform fine-grained rate limiting based on user ID or IP to underwrite that single-user abnormal behavior will not affect overall system performance.
Typical scenario: An infinite loop in a user's code caused continuous database calls, exhausting resources and incurring arrears before the platform reminder. After enabling rate limiting, the system will detect abnormal invocation methods in a short time frame and apply automatic throttling, keeping the loss within the acceptable range.
Fair resource allocation: Enhance overall user experience
Under high concurrency scenarios, a few users' high-frequency requests may occupy excessive resources, leading to poor user experience for most.
"Traffic throttling and frequency limiting" feature ensures fair resource allocation by limiting single-user request frequency to enhance overall service quality.
Typical scenario: In ecommerce platform flash sales, by setting a limit on request frequency for single users, it prevents "flash sale robots" (automated order grabbing programs) from resource preemption, ensuring general users have a fair opportunity to participate while maintaining stable operation during peak traffic periods.
Ops monitoring
Log Management
Feature definition
It provides comprehensive log collection, storage, retrieval, and analysis capabilities, supporting real-time log collection and centralized management for multiple cloud services such as SCF, cloud hosting, and cloud databases. This helps developers efficiently troubleshoot issues, monitor system operating status, and analyze business data. Depending on the version, it offers multiple log retention policies, ranging from short-term (2 hours for Personal Edition) to long-term data retention (7-180 days for Enterprise Edition).
Why It Is Needed to "Log Management" Feature
1. Troubleshoot: quickly locate anomalies
When an exception or error occurs in the system, no log records will cause troubleshooting difficulty and extend fault repair time.
The "log management" feature provides real-time log stream and advanced retrieval power, with time-based support, level, keyword, and multi-dimensional filtering to help developers quickly locate problems Root Cause.
Typical scenario: An e-commerce app encountered payment exceptions during promotional events. By retrieving error logs from the log management platform within the relevant time period, the third-party payment API timeout issue was identified and resolved in 10 minutes, preventing massive transaction loss.
Log retention period comparison: The personal edition's 2-hour log retention is suitable for real-time monitoring and instant troubleshooting. The enterprise edition's 7-180 day long-term log storage supports historical issue tracing, performance trend analysis, and compliance audit requirements.
2. Compliance and audit requirements
The finance, health care and other industries need to meet strict data retention and audit requirements, usually requiring operation logs to be kept for a long time.
Long-term log storage (30-180 days) meets regulatory compliance requirements and supports post-event audit and security incident investigation.
Typical scenario: Financial institutions need to retain user operation logs for at least 90 days to trace and investigate in case of disputes or security events.
Version selection suggestion: For organizational users requiring historical tracing, compliance audit or long-term data analysis, recommend choose the enterprise edition supporting longer log retention. For individual developers or scenarios only needing real-time monitoring, the personal edition's 2-hour log retention meets basic requirements.
Was this page helpful?
You can also Contact Sales or Submit a Ticket for help.
Yes
No
Feedback