The stand-alone version of HUAWEI CLOUD GaussDB (for Influx) is online, a powerful tool for reducing costs and increasing efficiency for enterprises

This article is shared from Huawei Cloud Community " Huawei Cloud GaussDB (for Influx) stand-alone version is online, a powerful tool for reducing costs and increasing efficiency for enterprises ", author: GaussDB database.

1. Background

The HUAWEI CLOUD GaussDB (for Influx) cluster version time-series database has built features such as high reliability, high availability, high performance, high scalability, and O&M-free, so that customers do not have to worry about database-level issues and can focus more on their own applications. Development and design have become the first choice for many customers.

Compared with traditional databases such as MySQL, "new" time-series databases are quite different in terms of design and use. The data model and usage methods are relatively unfamiliar to most developers, and more instances are needed for testing and debugging. In non-production environments, such as development and testing scenarios, there is no demand for performance and reliability, and cost becomes the primary consideration; if you choose to build your own environment for development and testing, although the cost problem is solved, maintenance is troublesome and operation It is complicated, and problems cannot be dealt with in time, which also greatly affects the efficiency of development and testing.

Therefore, GaussDB (for Influx) has launched a stand-alone version solution for use scenarios that do not require high performance and reliability and are cost-sensitive. This solution can be used in scenarios such as development and testing, and can not only enjoy the convenience brought by service, but also significantly reduce the cost of use.

2. The ultimate cost of GaussDB (for Influx) stand-alone version

When using databases, many customers feel that they can buy ECS to build a database without considering high availability, performance and scalability testing and development scenarios. Although this is troublesome, it can reduce the cost of use. After all, cloud databases are also based on Established by ECS, "bread" must be more expensive than "flour".

The GaussDB (for Influx) team combined the practical experience of many parties and comprehensively considered various factors such as cost, stability, and operability. To meet the needs of different scenarios, the following table lists the types of specifications supported by the stand-alone version and the corresponding fees:

Specification	Stand-alone version (yuan/month)	Self-built ECS (yuan/month)
4U8G	486.9	489
8U16G	973.8	950
16U32G	1947.6	1712
32U64G	3895.2	3396

Note: The cost comparison is only for computing resources, and storage resources are purchased on demand according to the amount of data

It can be seen that the price of the stand-alone version of GaussDB (for Influx) is basically the same as that of the self-built version . Under the 4U8G specification, it is even cheaper than buying ECS for the self-built version. The stand-alone version of GaussDB (for Influx) not only achieves the same price of "flour" and "bread", but also provides many service capabilities that self-built does not have.

3. Advantages of GaussDB (for Influx) stand-alone version

3.1 Cloud services are out-of-the-box, free of operation and maintenance

Although the database is basic software, its construction also requires a series of basic services as support. After purchasing ECS on the cloud, customers usually need to select the appropriate database version and modify the appropriate configuration parameters according to the current ECS specifications to achieve basic high availability. After completing the above work, it is necessary to build a monitoring system to ensure basic operation and maintenance. In contrast, customers who use cloud databases do not need to worry about the above-mentioned complicated work at all, and can concentrate on the realization and optimization of their own business, as shown in the following figure:

Especially when environments are created and deleted in batches and frequently, the above-mentioned manual operations will be particularly cumbersome, time-consuming and error-prone. After the database is created, the subsequent operation and maintenance is also a work that requires a lot of experience. If it is an unfamiliar database, a simple problem may block development and testing, and may eventually affect the overall progress of the project.

In contrast, the operation of cloud database is very simple and convenient. Just simply click on the page to purchase and create, select the corresponding storage size, and fill in the password, which greatly improves the operation efficiency. The most important thing is that when encountering problems, there is an experienced operation and maintenance team behind the cloud database to ensure that common problems can be recovered within minutes.

In addition to the convenience of use and deployment, the cloud database kernel has made many normative restrictions on unreasonable business use, so that customers can find problems in the business development and testing stages, and optimize and adjust them in time to ensure the formal business. Stablize.

3.2 Limit unreasonable queries

GaussDB (for Influx) has made many restrictions and specifications at the database kernel level. Unreasonable usage is not allowed, and optimization suggestions are given. Following these specifications can effectively improve the stability of business operations.

Disable query execution without a time range

Time series data has a strong time attribute, and the internal organization of the database is also strictly in accordance with the time attribute, which is very different from other databases. If you query without a time range, the database will query all data, which will most likely cause an OOM problem in the database and affect business stability.

Prohibit the execution of select * from statement query

Most real business scenarios need to specify specific query fields, but select * from is used for query due to various reasons such as development habits. This way of writing has two potential problems: 1. The return result may be uncertain. GaussDB (for Influx) is in schemaless mode, and tags and fields can be added or reduced at any time, so that the result returned by select* may change as the business changes. Inconsistencies may easily lead to exceptions when the business parses the returned results; 2 select* returns the values of all fields, but in fact only a few fields are useful, so a large amount of data transmission is invalid, wasting network bandwidth, and Waste computing, memory and other resources. Therefore, we do not recommend using this method of query in the development specification, and this query will also be intercepted in the kernel.

View slow log capability

The slow log capability of the cloud service enables timely discovery of slow queries during the business development phase and timely optimization and adjustment.

Limit the number of timelines and fields involved in each query

If a query involves too many timelines or fields, it means that the query may query too much data, and the database will load all the data into memory, which can easily lead to OOM and affect business stability. In most scenarios, too many timelines or fields are involved because the query statements we write are unreasonable, and further optimization is needed.

4. Summary

GaussDB (for Influx) is a cloud-native time-series database based on the separation of computing and storage architecture and compatible with the InfluxDB ecosystem. The stand-alone version model launched this time, while retaining the advantages of cloud databases, is basically the same as the price of self-built ECS to meet the needs of the business. Demand for low cost in scenarios that do not require high availability and reliability.

Click to follow and learn about Huawei Cloud's fresh technologies for the first time~