All Products
Search
Document Center

Advantages of TSDB for InfluxDB®️ over user-created InfluxDB databases

Last Updated: May 29, 2020

Features

Item InfluxDB databases created on physical servers purchased by the user InfluxDB databases created on ECS instances purchased by the user TSDB for InfluxDB® databases
Data reliability The data reliability is low even if a redundant array of independent disks (RAID) is used. Ultra disks are used to enable 99.9999999% data reliability. Ultra disks are used to enable 99.9999999% data reliability.
Service availability The service availability is low. Services may be interrupted due to power outage, server failures, disk failures, and even program failures. A process may be terminated due to improper parameter settings or instantaneous workload pressures. You have to create a complete process recovery mechanism.
Service termination caused by ECS instance failures are difficult to handle.
Optimal parameter settings are provided based on instance specifications and scenarios. A complete process recovery mechanism and an automatic ECS instance failover mechanism are provided.
In addition, TSDB for InfluxDB® provides a more sophisticated memory management mechanism that enables automatic load shedding to cope with instantaneous workload pressures.
TSDB for InfluxDB® automatically stops data writing when the disk is almost full.
System security You must deploy security systems for InfluxDB databases at a high cost and fix the vulnerabilities on your databases to ensure security. You must deploy security systems for InfluxDB databases at a high cost and fix the vulnerabilities on your databases to ensure security. The incoming traffic of TSDB for InfluxDB® databases is scrubbed to mitigate distributed denial-of-service (DDoS) attacks. Security vulnerabilities on the databases are also fixed in a timely manner.
Maintenance
You must maintain both hardware and software. Full-time database administrators (DBAs) who are familiar with InfluxDB are required but difficult to hire. You can perform basic management operations in a graphical console. You do not have to learn the complex commands of InfluxDB for basic operations.
Professional maintenance and consultation are provided 24 hours every day to free you from maintenance concerns.
Data backup You must back up your data on your own, allocate storage space to save backups, and check whether you can restore data from backups on a regular basis. You must back up your data on your own, allocate storage space to save backups, and check whether you can restore data from backups on a regular basis. In later versions, data will be automatically backed up.
Hot and cold data separation The open source InfluxDB does not support this feature. The open source InfluxDB does not support this feature. In later versions, cold data and hot data will be automatically separated.

Fees

Item InfluxDB databases created on physical servers purchased by the user InfluxDB databases created on ECS instances purchased by the user TSDB for InfluxDB® databases
Initial fees
(for a database with a quad-core CPU and 8 GB memory)
You must pay at least CNY 7,000 for low-configuration servers and pay for hardware such as switches, racks, and even data centers. It costs more than CNY 5,000 to purchase an ECS instance with a quad-core CPU and 8 GB memory for three years. You do not need to pay fees for hardware or network infrastructure.
You can also pay fees by month to prevent short-term financial pressure.
In most cases, the required fee is lower than that required by InfluxDB databases created on ECS instances purchased by the user.
You can also pay fees by month to prevent short-term financial pressure.
Subsequent fees You must pay a large volume of fees for power, data centers, bandwidth, and hardware maintenance.
A considerable DBA labor cost is also required.
A considerable DBA labor cost is required. No subsequent fees are incurred.


InfluxDB® is a trademark registered by InfluxData, which is not affiliated with, and does not endorse, TSDB for InfluxDB®.