What Is FlexusRDS?

Huawei Cloud Flexus is a next-generation out-of-the-box cloud service family designed for small- and medium-sized enterprises (SMEs) and developers. Huawei Cloud Flexus RDS (FlexusRDS) is a product in the Huawei Cloud Flexus family. FlexusRDS supports the following DB engines:

MySQL
PostgreSQL

How to Use FlexusRDS

You can use FlexusRDS DB instances in either of the following ways:

Management console: You can create and manage DB instances on the FlexusRDS console.
API: You can invoke APIs to create and manage DB instances. For details, see Huawei Cloud Flexus RDS API Reference.

FlexusRDS for MySQL

FlexusRDS for MySQL is a lightweight database based on the open-source MySQL kernel. It is designed for startups and individuals. It allows you to easily set up and manage DB instances and frees you to focus on your core business.

FlexusRDS for MySQL supports MySQL 8.0 and 5.7. For details about how to buy a FlexusRDS for MySQL DB instance, see Buying and Connecting to a FlexusRDS for MySQL DB Instance.

For more information, see the community documentation at https://dev.mysql.com/doc/.

FlexusRDS for PostgreSQL

FlexusRDS for PostgreSQL is a user-friendly and lightweight database designed for startups and individuals. Built on the open-source PostgreSQL kernel, it offers an out-of-the-box experience, freeing you from the hassle of maintenance and allowing you to focus on developing your business efficiently and reliably.

FlexusRDS for PostgreSQL supports PostgreSQL 16, 15, 14, 13, and 12. For details about how to buy a FlexusRDS for PostgreSQL DB instance, see Buying and Connecting to a FlexusRDS for PostgreSQL DB Instance.

For more information, see the community documentation at https://www.postgresql.org/docs/.

Basic Concepts

The smallest management unit of FlexusRDS is DB instance. A DB instance is an isolated database environment on the cloud. You can create and manage DB instances in FlexusRDS.

FlexusRDS DB instances are classified into single-node instances and primary/standby instances.

**Table 1** DB instance types
Type	Description	Notes
Single-node	A single-node architecture. It is less expensive than a primary/standby DB pair.	If a fault occurs on a single-node instance, the instance cannot recover in a timely manner.
Primary/Standby	An HA architecture. The primary and standby instances share the same IP address and can be deployed in different AZs.	When a primary instance is being created, a standby instance is provisioned synchronously to provide data redundancy. The standby instance is invisible to you after being created. If the primary instance fails, a failover occurs, during which database connection is interrupted. If there is a replication delay between the primary and standby instances, the failover takes an extended period of time. The client needs to be able to reconnect to the instance.

You can choose one of several database plans based on the vCPUs, memory, storage, and DB instance type you require. Table 2 lists the available FlexusRDS for MySQL database plans.

**Table 2** FlexusRDS for MySQL database plans
Instance Class	DB Instance Type
Standard 2U4G, 120 GB of storage	Single
Standard 2U8G, 240 GB of storage	Single
Standard 4U8G, 240 GB of storage	Single
High-availability 2U4G, 120 GB of storage	Primary/Standby
High-availability 2U8G, 240 GB of storage	Primary/Standby
High-availability 4U8G, 240 GB of storage	Primary/Standby

You can choose one of several database plans based on the vCPUs, memory, storage, and DB instance type you require. Table 3 lists the available FlexusRDS for PostgreSQL database plans.

**Table 3** FlexusRDS for PostgreSQL database plans
Instance Class	DB Instance Type
Standard 2U4G, 120 GB of storage	Single
Standard 2U8G, 240 GB of storage	Single
Standard 4U8G, 240 GB of storage	Single
High-availability 2U4G, 120 GB of storage	Primary/Standby
High-availability 2U8G, 240 GB of storage	Primary/Standby
High-availability 4U8G, 240 GB of storage	Primary/Standby

Automated backup is enabled by default when you create a FlexusRDS DB instance. The backup policy cannot be modified after instance creation.

Manual backups are user-initiated full backups of DB instances. You can download and delete manual backup as needed. Or if you want, you can keep the manual backups until you unsubscribe from your instance.

Differences Between FlexusRDS and RDS

**Table 4** Main differences
Item	FlexusRDS for MySQL	RDS for MySQL
Instance class	Minimum: 2 vCPUs and 4 GB of memory Maximum: 4 vCPUs and 8 GB of memory	More high instance classes are supported. For details, see RDS for MySQL Instance Classes.
Scalability	Read replicas are not supported. The storage can autoscale up to 4 TB for an instance.	Up to five read replicas can be added for a DB instance. The time required for adding read replicas depends on the data volume. Adding read replicas require additional storage. The storage can autoscale up to 4 TB for an instance.
Backup and restoration	Data can be restored to a specific point in time using full backups and binlog playback. Data can be restored to a new DB instance or the original DB instance.	Data can be restored to a specific point in time using full backups and binlog playback. Data can be restored to a new DB instance, the original DB instance, or any existing DB instance other than the original one. Database- and table-level recovery to any point in time is supported.
DB engine version	MySQL 5.7 and 8.0	MySQL 5.6, 5.7, and 8.0
Operation logs	Operation logs can be viewed on the FlexusRDS console.	Operation logs cannot be viewed on the RDS console. For details about task records, see Task Center.

**Table 5** Main differences
Item	FlexusRDS for PostgreSQL	RDS for PostgreSQL
Instance class	Minimum: 2 vCPUs and 4 GB of memory Maximum: 4 vCPUs and 8 GB of memory	More high instance classes are supported. For details, see RDS for PostgreSQL Instance Classes.
Scalability	Read replicas are not supported. The storage can autoscale up to 4 TB for an instance.	Up to five read replicas can be added for a DB instance. The time required for adding read replicas depends on the data volume. Adding read replicas require additional storage. The storage can autoscale up to 4 TB for an instance.
Backup and restoration	Data can be restored to a specific point in time using full backups and incremental backup playback. Data can be restored to a new DB instance.	Data can be restored to a specific point in time using full backups and incremental backup playback. Data can be restored to a new DB instance or any existing DB instance other than the original one. Database- and table-level recovery to any point in time is supported.
DB engine version	PostgreSQL 16, 15, 14, 13, and 12	PostgreSQL 16, 15, 14, 13, and 12 PostgreSQL 11, 10, 9.6, and 9.5 are only for installed base operations.
Operation logs	Operation logs can be viewed on the FlexusRDS console.	Operation logs cannot be viewed on the RDS console. For details about task records, see Task Center.

Product Advantages

Quick Setup
You can create a FlexusRDS DB instance anytime you want to on the console. You are advised to use Data Admin Service (DAS) to connect to your DB instance. DAS enables you to manage databases on a web-based console and provides you with database development, O&M, and intelligent diagnosis to make it easy to use and maintain your databases.
Solid Reliability
FlexusRDS automatically backs up data every day and stores backups as packages in Object Storage Service (OBS). Automated backups are retained for seven days and can be used to restore data within that period. This can meet your requirements for data restoration in most cases.

Point-in-time recovery (PITR) is supported. You can restore data to a new or original instance.
Storage Autoscaling
Storage autoscaling is disabled by default. You can enable it after purchasing a DB instance. With storage autoscaling enabled, FlexusRDS automatically scales up the storage of your instance when the storage usage reaches your preset limit. You can configure the upper limit and increment for autoscaling to keep up with your workload growth at a low cost.
High Security
FlexusRDS is protected by multiple layers of firewalls to defend against various malicious attacks, such as DDoS attacks and SQL injections.
Simplified O&M
With a web-based console, you can reboot DB instances, reset passwords, modify parameters, view error logs and slow query logs, and restore data. Instance metrics like CPU usage, IOPS, connections, and storage usage are monitored in real time, and an alarm is reported once any of the metrics becomes abnormal. You can always keep aware of your instance health.