Through the console, a full-featured JCS for MongoDB instance can be created in minutes, which can be put into use quickly to create value.
It supports elastic scalability. Users can upgrade or downgrade configurations according to business conditions to raise resource utilization rate and lower usage costs.
Provide abundant monitoring information and support the setting of multiple automatic alarm rules. Users can acquire the service running status at any time and place.
Automatically build a three-node replica set. The three data nodes are located on different physical servers and data synchronization is carried out automatically.
By default, Primary and Secondary nodes provide services. When the Primary node fails, the system automatically selects a new Primary node. When the Secondary node is unavailable, the standby node takes over the service. Service availability is ensured in multiple ways.
It supports multiple modes of availability zone deployment with nodes of replica set deployed in different availability zones, which can withstand data center-level faults.
Automatically backing up the data in full and keeping it for 7 days, and the backup file should be stored in cloud storage in three copies.
Support one-click restoration of backup data to the current instance. Users can also create a new JCS for MongoDB instance based on the backup data.
Supports one-click recovery of backing up the data to the current instance; in addition, it supports the creation of a new Cloud Database MongoDB instance based on the backup.
Instances are deployed in a user-customized VPC, and network isolation protection is performed directly at the TCP layer to ensure data security.
Support users to customize IP white list and carry out security control from access source.
JCS for MongoDB instance supports trans-AZ deployment to achieve disaster tolerance at the level of computer room. In trans-AZ deployment, the primary and secondary nodes and the hidden nodes of an instance are deployed in different AZs. When an AZ fails to serve due to force majeure, services can be shifted to another AZ quickly.
Relying on the complete backup mechanism of JCS for MongoDB, the data of one instance can be quickly synchronized into another database instance according to the capacity of backup of instance creation, so as to meet the demands of various application scenarios (e.g. game and other zones) for quick separation and integration.
Scan, feedback the current page