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, and GeminiDB Influx instances support both SSL and non-SSL connections. SSL is recommended to secure data transmission. |
|
Cross-AZ deployment |
GeminiDB can deploy nodes of an instance evenly across three AZs to provide cross-AZ DR. These AZs are physically isolated and can be interconnected 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: 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: Creating a DR Instance |
Cross-region Dual-active DR |
GeminiDB Cassandra API supports dual-active DR and bidirectional synchronization between two instances at different regions. Once one instance becomes faulty, the other takes over read/write traffic to ensure service continuity. |
GeminiDB Cassandra: Cross-region Dual-active DR |
Deletion protection |
GeminiDB can move unsubscribed yearly/monthly instances and deleted pay-per-use instances to Recycle Bin. This function enables you to restore instances deleted up to 7 days ago. |
|
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