tencent cloud

Service Registry and Governance

DocumentaçãoService Registry and GovernancePurchase GuidePolaris Polaris Product Edition and Pricing

Polaris Product Edition and Pricing

PDF
Modo Foco
Tamanho da Fonte
Última atualização: 2026-05-07 16:55:00
This document describes Tencent Service Framework (TSF) - Registration Configuration Governance - Polaris Product Version and Pricing.

Product Edition

Polaris is divided into Enterprise Edition, Standard Version (sold out), Basic Version, and Development Edition. Among them, the Development Edition is applicable only to non-production environments and product experience scenarios. Version comparison is as follows:
Primary Feature
Secondary Feature
Enterprise Edition
Standard Edition (Sold Out)
Basic Edition
Applicable scenario
Suitable for production environments that have higher requirements for performance and advanced Ops capabilities. Includes all capabilities of the service governance center: registry, configuration center, and governance center.
Suitable for production environments and includes registry, configuration center, and basic service governance capabilities.
Suitable for production environments, includes registry and configuration center, but lacks service governance capabilities.
Instance type
Dedicated instance
Dedicated instance
Dedicated instance
Access Mode
Multi-language SDK
Java/Go
Development framework
Spring Cloud/Dubbo/gRPC
API
HTTP/gRPC
Service management
Service Registration
Supported
Supported
Supported
Service Discovery
Supported
Supported
Supported
Health Check
Supported
Supported
Supported
Metadata Management
Supported
Supported
Supported
Service contract management
Under development
Under development
Under development
Traffic Management
CLB
Supported
Supported
Supported
QPS throttling
Supported
Not supported
Not supported
Warm-up
Supported
Not supported
Not supported
Concurrency throttling
Under development
Not supported
Not supported
Adaptive throttling
Under development
Not supported
Not supported
Overload protection
Under development
Not supported
Not supported
Hotspot throttling
Supported
Not supported
Not supported
Distributed traffic throttling (cluster)
Supported
Not supported
Not supported
Tag-based routing (metadata routing)
Supported
Supported
Supported
Dynamic routing
Supported
Supported
Not supported
Message canary release
Under development
Not supported
Not supported
Fault tolerance
Service-level/API-level circuit breaking
Supported
Not supported
Not supported
Outlier instance removal
Supported
Not supported
Not supported
Service instance isolation
Supported
Supported
Supported
Custom degradation
Supported
Not supported
Not supported
Null-push protection
Supported
Supported
Supported
Scenario-based features
Zero-downtime service launch
Supported
Supported
Not supported
Zero-downtime service deregistration
Supported
Supported
Not supported
Proximity-based routing
Supported
Supported
Not supported
Canary release
Supported
Supported
Not supported
End-to-end canary release
Supported
Not supported
Not supported
Configuration Management
Configuration Management
Supported
Supported
Supported
Configuration version
Supported
Supported
Supported
Rolling back configurations
Supported
Supported
Supported
Comparing configurations
Supported
Supported
Supported
Configuration canary release
Under development
Under development
Under development
Encrypting configurations
Under development
Under development
Under development
Configuration delivery trace
Under development
Under development
Under development
Observability
Engine system monitoring
Supported
Supported
Supported
Monitoring service registration and configuration
Supported
Supported
Supported
Service invocation monitoring
Supported
Supported
Not supported
Flow control monitoring
Supported
Supported
Not supported
Event Center
Supported
Supported
Supported
Logs
Supported
Supported
Supported
Operation Records
Supported
Supported
Supported
Alarms
Supported
Supported
Supported
Permission control
Users, user groups, and access policies
Supported
Supported
Supported
High availability
Multi-AZ deployment for the compute layer
Supported
Supported
Supported
Cross-city disaster recovery for the storage layer
Supported
Not supported
Not supported
Access throttling for the compute layer
Supported
Supported
Supported
Engine Management
Version upgrade
Supported
Supported
Supported
Zero-downtime scaling
Supported
Supported
Supported
Create/delete/restart
Supported
Supported
Supported
Public network switch
Supported
Supported
Supported
Access allowlist/security group
Supported
Supported
Supported
Multiple VPCs
Supported
Supported
Supported
Configuring Engine Parameters
Supported
Supported
Supported

Pricing

The billable items for Polaris include service governance fees for all application nodes plus public network traffic fee (as needed).
Note:
The number of nodes refers to the number of clients connected to Polaris online, which is the number of application processes accessing the Polaris server. The types of clients that connect to Polaris include Polaris sdk, Polaris agent, sidecar, Polaris controller, and others.
The cost for TSF - Registration Configuration Governance - Polaris includes the cost of Polaris server-side resources (such as databases, CLB, and containers) and the cost of service governance. It does not include the cost of Tencent Cloud virtual machines, containers, and CLB instances used for deploying business applications.
The actual number of nodes used is calculated based on the peak value of the current month. It is recommended that the number of nodes you purchase exceeds the estimated peak number of nodes for the month and includes a buffer to accommodate business scaling.
Public network traffic fees are incurred only when clients access the Polaris server via a public network. Access via a private network does not incur these fees.
Polaris supports pay-as-you-go (postpaid) and annual/monthly subscription (prepayment) purchase methods.
Pay-as-you-go billing mode: You can enable/destroy instance at any time and pay by instance usage duration. Billing time granularity is accurate to the hour. Prepayment is unnecessary. Settlement occurs daily to effectively avoid resource waste.
Monthly subscription mode: Pay the fee when creating new instances. Suitable for long-term stable business scenarios with lower cost compared to pay-as-you-go mode.

Service Governance Cost

Monthly subscription (prepaid) mode
Billing Formula: Service governance fee = Unit price corresponding to version and number of nodes x Time (Minimum granularity: Month)
Pay-as-you-go (postpaid) mode
Billing Formula: Service governance fee = Unit price corresponding to version and number of nodes x Time (Minimum granularity: Hour)
Basic Edition
Enterprise Edition
Edition
Node quantity
Yearly/Monthly Subscription (USD/Month)
Pay-as-you-go (USD/Hour)
Basic Edition
500
135
0.377
Basic Edition
1000
275
0.71
Basic Edition
2000
485
1.35
Basic Edition
5000
1071
3.02
Basic Edition
10000
2057
5.95
Basic Edition
20000
3942.86
10.95
Monthly subscription (prepaid) mode billing example:
If you purchase the Basic Edition 500-node specification and run it for 2 months, the cost = 135 x 2 = USD 270.
Pay-as-you-go (postpaid) mode billing example:
If you purchase the Basic Edition 500-node specification and it runs for 2 hours, the cost = 0.377 x 2 = USD 0.754.
Edition
Node quantity
Yearly/Monthly Subscription (USD/Month)
Pay-as-you-go (USD/Hour)
Enterprise Edition
50
857.14
1.19
Enterprise Edition
100

1571.43

2.19
Enterprise Edition
200

2828.57


3.94

Enterprise Edition
500

6171.43


8.58

Enterprise Edition
1000

12114.29


16.81

Enterprise Edition
2000

23714.29


32.95

Enterprise Edition
5000

58114.29


80.71

Enterprise Edition
10000

113914.29


158.20

Enterprise Edition
20000

225142.86


312.70

Enterprise Edition
50000

558114.29


775.18

Monthly subscription (prepaid) mode billing example:
If you purchase the Enterprise Edition 500-node specification and run it for 1 year (12 months), the cost = 6171.43 x 12 = USD 74,057.16.
Pay-as-you-go (postpaid) mode billing example:
If you purchase the Enterprise Edition 500-node specification and it runs for 2 hours, the cost = 8.58 x 2 = USD 17.16.
Note:
After you purchase a pay-as-you-go instance, the system allocates related instance resources. Regardless of whether you use the instance and related resources, fees are settled by hour. If the instance is no longer required, release it to prevent fees from being generated continuously.

Public Network Traffic Fee

The current public network bandwidth uses the hourly bandwidth billing mode.
Hourly bandwidth
Fees are charged based on the duration of public network bandwidth usage, the payment mode is postpaid, and fees are settled hourly. Suitable for usage scenarios with relatively stable peak business traffic at different times and short-term usage.
Billing Price
Bandwidth
Unit Price (USD/Mbps/Hour)
≤5Mbps
0.0064
>5Mbps
0.0232
Billing example: If you select By Hourly Bandwidth and purchase a fixed bandwidth of 6 Mbps, the total fees are calculated as follows: 5Mbps × 0.0064 USD/Mbps/hour + (6Mbps - 5Mbps) × 0.0232 USD/Mbps/hour = 0.0552 USD/hour.

Anterior: Comparison with Self-Built GatewaysPróximo: Polaris Performance Evaluation

Ajuda e Suporte

Esta página foi útil?

comentários