Data Protection
GeminiDB provides a series of features to ensure data security and reliability.
Feature |
Description |
Reference |
---|---|---|
Secure Sockets Layer (SSL) |
GeminiDB Redis, GeminiDB Mongo, GeminiDB Cassandra, GeminiDB Influx, GeminiDB DynamoDB-Compatible, and GeminiDB HBase instances support both SSL and non-SSL connections. SSL is recommended to secure data transmission. |
|
Cross-AZ deployment |
GeminiDB allows you to deploy nodes of an instance evenly across three AZs to provide cross-AZ DR. These AZs are physically isolated using hash functions and can be connected over private networks. |
|
Load balancing |
GeminiDB Redis API supports load balancing. Data access requests can be evenly routed to different nodes in a cluster to avoid hotspots and maximize overall throughput of the cluster. |
GeminiDB Redis instance: Connecting to an Instance Using a Load Balancer Address |
Intra-region DR |
Primary GeminiDB Cassandra instances support HA. If a primary instance fails to be connected due to a natural disaster, services can be switched over to its DR instance. |
GeminiDB Cassandra instance: Creating a DR Instance |
Cross-region active-active DR |
GeminiDB Cassandra API supports active-active DR and bidirectional synchronization between two instances in different regions. Once an instance becomes faulty, the other takes over its workloads to ensure service continuity. |
GeminiDB Cassandra instance: Cross-region Dual-active DR |
Deletion protection |
You can move unsubscribed yearly/monthly and deleted pay-per-use GeminiDB instances to the recycle bin. Instances in the recycle bin can be retained for up to 7 days. |
|
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.
For any further questions, feel free to contact us through the chatbot.
Chatbot