tencent cloud

TencentDB for MongoDB

Release Notes and Announcements
Release Notes
Announcements
User Guide
Product Introduction
Overview
Strengths
Use Cases
Cluster Architecture
Product Specifications
Features
Regions and AZs
Terms
Service Regions and Service Providers
Purchase Guide
Billing Overview
MongoDB Pricing
Billing Formula
Payment Overdue
Backup Space Billing
Configuration Adjustment Billing
Getting Started
Quickly Creating an Instance
Connecting to a TencentDB for MongoDB Instance
Reading/Writing Database
Operation Guide
Access Management
Instance Management
Node Management
Version Upgrade
Network Configuration
Monitoring
Backup and Rollback
Database Audit
Data Security
SSL Authentication
Log Management
Database Management
Multi-AZ Deployment
Disaster Recovery/Read-Only Instances
Parameter Configuration
Recycle Bin
Task Management
Performance Optimization
Data Migration Guide
Practical Tutorial
Optimizing Indexes to Break Through Read/Write Performance Bottlenecks
Troubleshooting Mongos Load Imbalance in Sharded Cluster
Considerations for Using Shard Clusters
Sample of Reading and Writing Data in MongoDB Instance
Methods for Importing and Exporting Data Based on CVM Connected with MongoDB
What to Do for Errors of Repeated Instance Creation and Deletion of Databases with the Same Names?
Troubleshooting MongoDB Connection Failures
Shard Removal Task: Guide for Confirming the Progress and Troubleshooting Issues
Performance Fine-Tuning
Ops and Development Guide
Development Specifications
Command Support in Sharded Cluster v3.2
Command Support in v3.6
Development Ops
Troubleshooting
Increased Slow Queries
Number of Connections Exceeding Limit
API Documentation
History
Introduction
API Category
Making API Requests
Instance APIs
Backup APIs
Account APIs
Other APIs
Task APIs
Introduction
Data Types
Error Codes
Instance Connection
Shell Connection Sample
PHP Connection Sample
Node.js Connection Sample
Java Connection Sample
Python Connection Sample
Python Read/Write Sample
Go Connection Sample
PHP Reconnection Sample
Product Performance
Test Environment
Test Method
Test Result
FAQs
Cost
Features
Sharded Cluster
Instance
Rollback and Backup
Connection
Data Migration
Others
Service Agreement
Service Level Agreement
Terms of Service
Glossary
Contact Us

Strengths

PDF
Mode fokus
Ukuran font
Terakhir diperbarui: 2026-01-19 17:11:37

Strengths of TencentDB for MongoDB

TencentDB for MongoDB provides the capabilities of NoSQL databases as a service, which has great strengths in terms of flexibility, ease of use, high availability, fully managed Ops, data security, and data reliability.

High flexibility and ease of use

TencentDB for MongoDB is fully compatible with the open-source MongoDB protocol, so you can directly use MongoDB clients to communicate with TencentDB for MongoDB instances and migrate existing MongoDB applications to the cloud with no need to make any code modifications.
TencentDB for MongoDB supports multiple system architectures to meet the needs in different business scenarios, including replica set and sharded cluster. You can deploy the most appropriate architecture according to your actual use case and adjust the configuration specifications promptly to adapt to use case changes.
You can directly purchase TencentDB for MongoDB cluster instances on the purchase page, select the desired system architecture, and access the instances through URI with no need to install them on your own.

High availability

The service can be deployed in a distributed cluster across AZs in a region-specific manner. This guarantees high service availability, and even failovers will not affect your normal business operations.
With high-performance storage servers, the cluster can be quickly and elastically scaled to maintain a high throughput and an unlimited storage capacity when massive amounts of data are retained.

Fully managed service

TencentDB for MongoDB is completely imperceptible to businesses. You can configure alarm rules with more than 20 automated monitoring metrics. This helps you stay up to date with the running status of your instances and promptly prevent risks.
TencentDB for MongoDB offers a complete set of management APIs to implement diverse self-service resource management and Ops features.

High security and reliability

Network protection: TencentDB for MongoDB supports configuring security groups in VPCs to implement allowlist-enabled network access control, which ensures the security and reliability of network environments.
Account authorization: TencentDB for MongoDB allows you to authorize root accounts, sub-accounts, or across accounts, so you can manage your resources at a fine-grained level and benefit from enterprise-grade security protection.
Automatic backup: TencentDB for MongoDB supports multi-node data backup. It provides at least three online replicas of data storage to ensure data security and uses the data backup mechanism to store backup data for days and restore data in case of disasters.
Data isolation: TencentDB for MongoDB supports multiple layers of data isolation between different regions, AZs, networks, and account levels to ensure the data security and integrity.

Differences Between TencentDB for MongoDB and Self-Built MongoDB

TencentDB for MongoDB offers special optimizations to solve issues which often occur during the operations of traditional self-built MongoDB instances, such as performance bottlenecks, Ops difficulties, as well as data reliability and availability problems. This makes it easier to deploy, manage, and scale instances. In addition, you can apply for required resources based on your actual business conditions and pay only for what you use in a more cost-effective way.
Dimension
TencentDB for MongoDB
Self-Built MongoDB
Cost-effectiveness
You don't have to invest in hardware and software. Multiple specification options (such as High IO and Ten-Gigabit High IO) are available for your choice. You can apply for required resources based on your actual business conditions and pay only for what you use.
A single storage server is costly. If you want a high-availability primary/secondary instance (replica set), you will have to purchase three servers, which may cause resource redundancy and waste. In addition, you need to recruit professional database administrators, which also means high labor costs.
Service availability
Hot backup is supported based on two or more servers, with automatic disaster recovery, failover, and imperceptible migration features available. In addition, the same read preference from the secondary databases as the native MongoDB is offered to ensure high read concurrency capability.
You need to fix failures and build primary/secondary replica cluster architecture and RAID on your own.
Data reliability
The system ensures exceptional data reliability, featuring a comprehensive automatic backup mechanism and lossless recovery capabilities. With real-time hot standby support, data can be restored to any point within the last 5 days (Note: If the volume of operations between two backup points exceeds the oplog capacity, restoration to intermediate time points between backups will not be possible).
You need to protect your data on your own, and the data reliability is subject to hardware failure rate and database management skills of technical personnel.
System security
DDoS protection and fixes of various database and host security vulnerabilities are provided automatically.
You need to fix vulnerabilities on your own.
Real-time monitoring
Multidimensional monitoring and automatic failure alarming are available in an unattended manner.
You need to develop your own monitoring system, and Ops personnel are often required to fix failures overnight, which incurs high Ops costs.
Business scaling
Quick scaling is available for fast deployment and service launch.
You need to procure hardware, host data centers, redeploy applications, and complete other tedious work on your own, which makes business scaling much slower.
Resource utilization
Resource requests can be made on demand to achieve 100% resource utilization.
Business peaks are prone to leading to low average load and low resource utilization.
Performance bottleneck
New PCI-E SSD storage media and new-gen storage engines are adopted, with customizable performance tuning features to help improve the performance of specific components.
The open-source MongoDB is not specifically optimized, and its use is limited in certain scenarios.

Bantuan dan Dukungan

Apakah halaman ini membantu?

masukan