Functions_Service Overview_GeminiDB-Huawei Cloud

With a cloud native distributed architecture, GeminiDB Redis API is fully compatible with Redis and supports various data types. GeminiDB Redis instance data can be stored in persistent storage in real time and backed up automatically, using strong consistency, three-copy storage. The system continuously monitors instance statuses. You can scale compute nodes and storage as needed.

Billing modes

Two billing modes are provided:

Yearly/Monthly: If your future usage is predictable, this billing mode is generally less expensive than pay-per-use. Longer subscriptions offer larger discounts.

Pay-per-use (hourly): You are only billed for how long you have actually used your instance. This mode can be a good option when future requirements are unpredictable. Pay-per-use instances are priced by the hour, but if an instance is used for less than one hour, you will be billed based on the actual duration.

You can switch between the yearly/monthly and pay-per-use modes.

Enabling public access

You can bind an EIP to access an instance over a public network or unbind the EIP from the instance if necessary. If an instance has already been bound with an EIP, unbind the EIP from it first before binding a new EIP. For details, see Binding an EIP to a GeminiDB Redis Instance Node.

Scaling storage

You can scale up storage if it cannot accommodate to your increasing workloads. If an instance status is Storage full and data cannot be written to databases, you need to scale up storage.

As data volumes decrease, you can scale down storage to avoid low database node utilization and resource waste.

Scaling storage does not interrupt your services, and you do not need to restart your instance. For details, see Scaling Storage.

Changing vCPUs and memory

You can change vCPUs and memory of an instance. If the instance status changes from Changing instance class to Available, the change is successful. For details, see Changing vCPUs and memory.

Backup and restoration

You can create a manual or an automated backup policy for your database. If a database is faulty or data is damaged, you can restore it from backups to ensure data reliability.

Parameter template management

You can use database parameter templates to manage DB engine configurations. A database parameter template acts as a container for engine configuration values that can be applied to one or more DB instances.

When creating an instance, you can specify a default or custom parameter template. After an instance is created, you can also change its associated parameter template.

Each default parameter template contains database engine defaults and database system defaults.

To use your custom parameter settings, create a parameter template and apply it to your instance.

Monitoring and alarms

Cloud Eye monitors your instance status. You can view instance metrics on the console.

There is a short delay before monitoring data is displayed on Cloud Eye,

so the data of a new instance takes 5 to 10 minutes to show up. You can also set alarm rules to specify monitored objects and notification policies. In this way, you can stay on top of your instance status.

API

This document describes how to use APIs to perform operations on GeminiDB instances, such as instance creation, backup and restoration, query, parameter modification, and deletion.

GeminiDB DynamoDB-Compatible API is an in-house distributed database service with decoupled storage and compute. It is embedded in kernel services of GeminiDB Cassandra API and fully compatible with Amazon DynamoDB. The instances can be deployed, backed up, or restored quickly. They deliver high availability, top-tier security, seamless scalability, and exceptional performance to meet diverse needs. Alarms will be triggered whenever certain metric thresholds are reached by your instance.

Billing modes

Two billing modes are provided:

Yearly/Monthly: If your future usage is predictable, this billing mode is generally less expensive than pay-per-use. Longer subscriptions offer larger discounts.

Pay-per-use (hourly): You are only billed for how long you have actually used your instance. This mode can be a good option when future requirements are unpredictable. Pay-per-use instances are priced by the hour, but if an instance is used for less than one hour, you will be billed based on the actual duration.

You can switch between the yearly/monthly and pay-per-use modes.

Enabling public access

You can bind an EIP to access an instance over a public network or unbind the EIP from the instance if necessary. If an instance has already been bound with an EIP, unbind the EIP from it first before binding a new EIP. For details, see Binding an EIP to a GeminiDB DynamoDB-Compatible Instance Node.

Scaling storage

You can scale up storage if it cannot accommodate to your increasing workloads. If an instance status is Storage full and data cannot be written to databases, you need to scale up storage.

As data volumes decrease, you can scale down storage to avoid low database node utilization and resource waste.

Scaling storage does not interrupt your services, and you do not need to restart your instance. For details, see Scaling Storage.

Changing vCPUs and memory

You can change vCPUs and memory of an instance. If the instance status changes from Changing instance class to Available, the change is successful. For details, see Changing vCPUs and Memory.

Backup and restoration

You can create a manual or an automated backup policy for your database. If a database is faulty or data is damaged, you can restore it from backups to ensure data reliability.

Monitoring and alarms

Cloud Eye monitors your instance status. You can view instance metrics on the console.

There is a short delay before monitoring data is displayed on Cloud Eye, so the data of a new instance takes 5 to 10 minutes to show up.

You can also set alarm rules to specify monitored objects and notification policies. In this way, you can stay on top of your instance status.

API

This document describes how to use APIs to perform operations on GeminiDB instances, such as instance creation, backup and restoration, query, parameter modification, and deletion.

GeminiDB Cassandra API is a Huawei-developed cloud-native, distributed NoSQL database service with decoupled storage and compute. It is compatible with the Cassandra ecosystem and supports Cassandra Query Language (CQL), a query language with SQL-like syntax. It is secure, reliable, scalable, and easy to manage and can provide high I/O performance.

Billing modes

Two billing modes are provided:

Yearly/Monthly: If your future usage is predictable, this billing mode is generally less expensive than pay-per-use. Longer subscriptions offer larger discounts.

Pay-per-use (hourly): You are only billed for how long you have actually used your instance. This mode can be a good option when future requirements are unpredictable. Pay-per-use instances are priced by the hour, but if an instance is used for less than one hour, you will be billed based on the actual duration.

You can switch between the yearly/monthly and pay-per-use modes.

Enabling public access

You can bind an EIP to access an instance over a public network or unbind the EIP from the instance if necessary. If an instance has already been bound with an EIP, unbind the EIP from it first before binding a new EIP. For details, see Binding an EIP to a GeminiDB Cassandra Instance Node.

Scaling storage

You can scale up storage if it cannot accommodate to your increasing workloads. If an instance status is Storage full and data cannot be written to databases, you need to scale up storage.

As data volumes decrease, you can scale down storage to avoid low database node utilization and resource waste.

Scaling storage does not interrupt your services, and you do not need to restart your instance. For details, see Scaling Storage.

Changing vCPUs and memory

You can change vCPUs and memory of an instance. If the instance status changes from Changing instance class to Available, the change is successful. For details, see Changing vCPUs and Memory.

Backup and restoration

You can create a manual or an automated backup policy for your database. If a database is faulty or data is damaged, you can restore it from backups to ensure data reliability.

Parameter template management

You can use database parameter templates to manage DB engine configurations. A database parameter template acts as a container for engine configuration values that can be applied to one or more DB instances.

When creating an instance, you can specify a default or custom parameter template. After an instance is created, you can also change its associated parameter template.

Each default parameter template contains database engine defaults and database system defaults.

To use your custom parameter settings, create a parameter template and apply it to your instance.

Monitoring and alarms

Cloud Eye monitors your instance status. You can view instance metrics on the console.

There is a short delay before monitoring data is displayed on Cloud Eye, so the data of a new instance takes 5 to 10 minutes to show up.

You can also set alarm rules to specify monitored objects and notification policies. In this way, you can stay on top of your instance status.

API

This document describes how to use APIs to perform operations on GeminiDB instances, such as instance creation, backup and restoration, query, parameter modification, and deletion.

GeminiDB HBase API is based on GeminiDB Cassandra API. They share some cluster components, but GeminiDB HBase API introduces its own advanced features. Apache HBase Driver can be directly connected using the right protocol, so you can smoothly migrate data to GeminiDB HBase instances without refactoring. GeminiDB HBase API delivers high availability, top-tier security, seamless scalability, and exceptional performance to meet diverse needs. It also provides automated management and O&M functions, such as cluster scaling in minutes, automated backup, fault detection, and multi-AZ fault tolerance.

Billing modes

Two billing modes are provided:

Yearly/Monthly: If your future usage is predictable, this billing mode is generally less expensive than pay-per-use. Longer subscriptions offer larger discounts.

Pay-per-use (hourly): You are only billed for how long you have actually used your instance. This mode can be a good option when future requirements are unpredictable. Pay-per-use instances are priced by the hour, but if an instance is used for less than one hour, you will be billed based on the actual duration.

You can switch between the yearly/monthly and pay-per-use modes.

Scaling storage

You can scale up storage if it cannot accommodate to your increasing workloads. If an instance status is Storage full and data cannot be written to databases, you need to scale up storage.

As data volumes decrease, you can scale down storage to avoid low database node utilization and resource waste.

Scaling storage does not interrupt your services, and you do not need to restart your instance. For details, see Scaling Storage.

Changing vCPUs and memory

You can change vCPUs and memory of an instance. If the instance status changes from Changing instance class to Available, the change is successful. For details, see Changing vCPUs and Memory.

Backup and restoration

You can create a manual or an automated backup policy for your database. If a database is faulty or data is damaged, you can restore it from backups to ensure data reliability.

Monitoring and alarms

Cloud Eye monitors your instance status. You can view instance metrics on the console.

There is a short delay before monitoring data is displayed on Cloud Eye, so the data of a new instance takes 5 to 10 minutes to show up.

You can also set alarm rules to specify monitored objects and notification policies. In this way, you can stay on top of your instance status.

API

This document describes how to use APIs to perform operations on GeminiDB instances, such as instance creation, backup and restoration, query, parameter modification, and deletion.

GeminiDB Influx API is a cloud-native, InfluxDB-compatible NoSQL time series database service, which uses a Huawei-developed architecture with decoupled storage and compute. GeminiDB Influx API allows concurrent time series data reads/writes, ensures high compression ratio storage, and aggregates data from multiple dimensions. GeminiDB Influx instances can be deployed, backed up, or restored quickly. Compute and storage resources can be added separately. Alarms will be triggered whenever instance metrics reach certain thresholds. It is ideal for scenarios such as service monitoring and analysis, real-time IoT device monitoring, industrial production monitoring, production quality evaluation, and fault backtracking.

Billing modes

Two billing modes are provided:

Yearly/Monthly: If your future usage is predictable, this billing mode is generally less expensive than pay-per-use. Longer subscriptions offer larger discounts.

Pay-per-use (hourly): You are only billed for how long you have actually used your instance. This mode can be a good option when future requirements are unpredictable. Pay-per-use instances are priced by the hour, but if an instance is used for less than one hour, you will be billed based on the actual duration.

You can switch between the yearly/monthly and pay-per-use modes.

Enabling public access

You can bind an EIP to access an instance over a public network or unbind the EIP from the instance if necessary. If an instance has already been bound with an EIP, unbind the EIP from it first before binding a new EIP. For details, see Binding an EIP to a GeminiDB Influx Instance Node.

Scaling storage

You can scale up storage if it cannot accommodate to your increasing workloads. If an instance status is Storage full and data cannot be written to databases, you need to scale up storage.

As data volumes decrease, you can scale down storage to avoid low database node utilization and resource waste.

Scaling storage does not interrupt your services, and you do not need to restart your instance. For details, see Scaling Storage.

Changing vCPUs and memory

You can change vCPUs and memory of an instance. If the instance status changes from Changing instance class to Available, the change is successful. For details, see Changing vCPUs and Memory.

Backup and restoration

You can create a manual or an automated backup policy for your database. If a database is faulty or data is damaged, you can restore it from backups to ensure data reliability.

Parameter template management

You can use database parameter templates to manage DB engine configurations. A database parameter template acts as a container for engine configuration values that can be applied to one or more DB instances.

When creating an instance, you can specify a default or custom parameter template. After an instance is created, you can also change its associated parameter template.

Each default parameter template contains database engine defaults and database system defaults.

To use your custom parameter settings, create a parameter template and apply it to your instance.

Monitoring and alarms

Cloud Eye monitors your instance status. You can view instance metrics on the console.

There is a short delay before monitoring data is displayed on Cloud Eye, so the data of a new instance takes 5 to 10 minutes to show up.

You can also set alarm rules to specify monitored objects and notification policies. In this way, you can stay on top of your instance status.

API

This document describes how to use APIs to perform operations on GeminiDB instances, such as instance creation, backup and restoration, query, parameter modification, and deletion.

GeminiDB Mongo API is a cloud-native, MongoDB-compatible NoSQL time series database service, which uses a Huawei-developed architecture with decoupled storage and compute. The instances can be deployed, backed up, or restored quickly. They deliver high availability, top-tier security, seamless scalability, and exceptional performance to meet diverse needs. Alarms will be triggered whenever certain metric thresholds are reached by your instance.

Enabling public access

You can bind an EIP to access an instance over a public network or unbind the EIP from the instance if necessary. If an instance has already been bound with an EIP, unbind the EIP from it first before binding a new EIP. For details, see Binding an EIP.

Scaling up storage

You can scale up storage if it cannot accommodate to your increasing workloads. If an instance status is Storage full and data cannot be written to databases, you need to scale up storage.

Scaling up storage does not interrupt your services, and you do not need to restart your instance. For details, see Scaling Up Storage.

Changing vCPUs and memory

You can change vCPUs and memory of an instance. If the instance status changes from Changing instance class to Available, the change is successful. For details, see Changing vCPUs and Memory.

Monitoring and alarms

Cloud Eye monitors your instance status. You can view instance metrics on the console.

There is a short delay before monitoring data is displayed on Cloud Eye, so the data of a new instance takes 5 to 10 minutes to show up.

You can also set alarm rules to specify monitored objects and notification policies. In this way, you can stay on top of your instance status.

API

This document describes how to use APIs to perform operations on GeminiDB instances, such as instance creation, backup and restoration, query, parameter modification, and deletion.

Functions

Feedback

Was this page helpful?