ApsaraDB for MongoDB is fully compatible with the MongoDB protocol. Built on the Apsara distributed operating system and a high-reliability storage engine, it provides multi-node high availability, elastic scaling, disaster recovery, backup and restoration, and performance optimization.
Deployment architectures
ApsaraDB for MongoDB supports three deployment architectures:
| Architecture | Use case | Details |
|---|---|---|
| Standalone | Development, testing, and non-core data storage | Standalone instances |
| Replica set | Production workloads with automatic failover | Replica set instances |
| Sharded cluster | Large-scale applications with high throughput demands | Sharded cluster instances |
Elastic scaling
Change the instance type, storage capacity, and number of nodes at any time. Schedule changes during off-peak hours to minimize disruptions. Overview.
Network security
| Feature | Description |
|---|---|
| Anti-DDoS | Monitors inbound traffic in real time. Scrubs malicious traffic by filtering source IP addresses. Triggers blackhole filtering when scrubbing is insufficient. |
| IP address whitelists | Restrict access by specifying allowed IP addresses. Each whitelist supports up to 1,000 IP addresses and CIDR blocks. Modify the IP address whitelist of an ApsaraDB for MongoDB instance. |
| VPC | Deploy instances in a VPC for network isolation with higher security and performance than the classic network. Create a VPC before deploying instances. Default VPCs and default vSwitches. |
Data encryption
| Feature | Description |
|---|---|
| SSL encryption | Encrypts network connections at the transport layer to protect data in transit. Configure SSL encryption for an ApsaraDB for MongoDB instance. |
| TDE | Transparent data encryption (TDE) encrypts data files during I/O—data is encrypted on write and decrypted on read. TDE does not increase file size or require application changes. Configure TDE for an ApsaraDB for MongoDB instance. |
Backup and recovery
| Feature | Description |
|---|---|
| Automatic backup | Configure a backup window to run backups automatically during off-peak hours. Configure automatic backup for an instance. |
| Manual backup | Create physical or logical backups on demand. Manually back up the data of an ApsaraDB for MongoDB instance. |
| Data restoration | Restore data from a backup point or a point in time. Restore by backup point. Restore by point in time. |
| Backup download | Download backup files to a local machine within the retention period. Download backup files. |
Multi-zone disaster recovery
Distribute nodes across multiple zones for high reliability and data protection. Select multiple zones during instance creation.
| Capability | Details |
|---|---|
| Multi-zone replica set | Create a multi-zone replica set instance |
| Multi-zone sharded cluster | Create a multi-zone sharded cluster instance |
| Zone migration | Migrate a replica set instance from a single zone to multiple zones. Migrate an ApsaraDB for MongoDB instance to a different zone. |
Zone migration is available only for replica set instances running MongoDB 4.2 or earlier without TDE enabled.
Monitoring
ApsaraDB for MongoDB tracks up to 20 system metrics, including disk usage, IOPS, connections, CPU utilization, network traffic, TPS, QPS, and cache hit ratio. Basic monitoring.
Data management and migration tools
Data Management (DMS)
Data Management (DMS) manages relational databases (MySQL, SQL Server, PostgreSQL), NoSQL databases (MongoDB, Redis), and Linux servers. Features include data management, schema management, server management, access control, BI charts, trend analysis, data tracking, and performance monitoring and optimization. What is DMS?
Data Transmission Service (DTS)
Data Transmission Service (DTS) exchanges data between relational databases, NoSQL databases, and OLAP systems. DTS provides:
-
Data migration, including zero-downtime migration
-
Real-time data synchronization, including cross-border synchronization
-
Real-time data subscription
-
Geo-disaster recovery and cache refreshing