TSDB for InfluxDB®️ vs. self-managed InfluxDB
更新时间:
复制 MD 格式
InfluxDB® is a trademark registered by InfluxData, which is not affiliated with, and does not endorse, TSDB for InfluxDB®.
Use this page to compare TSDB for InfluxDB® — Alibaba Cloud's managed time series database — against two self-managed deployment options: InfluxDB on your own hardware, or InfluxDB on Elastic Compute Service (ECS) instances.
Capability comparison
| Capability | Self-managed on hardware | Self-managed on ECS | TSDB for InfluxDB® |
|---|---|---|---|
| Reliability | Low. Data loss can occur even with redundant arrays of independent disks (RAID). | Ultra disks provide 99.9999999% reliability. | Ultra disks provide 99.9999999% reliability. |
| Availability | Low. Service interruptions can result from power, server, disk, or application failures. | Processes can stop due to parameter errors or traffic spikes. You must configure a restore mechanism. If an ECS instance fails, the database is unavailable until the instance is recovered. | Automatic parameter tuning based on your instance specification and your business scenario. Built-in process recovery and ECS-level failover. Advanced memory management compared to open source InfluxDB. Automatic load shedding during traffic spikes. Write protection when disk capacity is running low. |
| Security | You are responsible for deploying a defense system and patching security vulnerabilities — both at significant cost. | You are responsible for deploying a defense system and patching security vulnerabilities — both at significant cost. | DDoS protection and traffic scrubbing are included. Security patches are applied in real time. |
| Operations and maintenance (O&M) | You must maintain both software and hardware. Administration is complex and time-consuming. | At least one engineer with deep InfluxDB knowledge must serve as a dedicated database administrator (DBA). | A graphical console lets you manage databases without complex commands. You do not need to be an expert at using complex commands to manage your InfluxDB databases. 24/7 technical support is included. |
| Data backup | Manual backups, storage allocation, and periodic validity checks are your responsibility. | Manual backups, storage allocation, and periodic validity checks are your responsibility. | Automatic backup will be available in a future version. |
| Hot and cold data separation | Open source InfluxDB does not support separating or tiering hot and cold data. | Open source InfluxDB does not support separating or tiering hot and cold data. | Automatic hot and cold data separation will be available in a future version. |
Pricing comparison
The estimates below use a 4-core, 8 GB memory server specification as a reference point.
| Cost | Self-managed on hardware | Self-managed on ECS | TSDB for InfluxDB® |
|---|---|---|---|
| Initial cost | More than USD 1,100 for a low-spec server, plus hardware infrastructure (switches, racks, data center). | Approximately USD 850 for a one-year ECS subscription (4 cores, 8 GB memory). No hardware purchase required. Monthly billing available. | Lower than the ECS-based self-managed option. Monthly billing available. |
| Ongoing costs | Power, data center, bandwidth, hardware repair and replacement, plus DBA labor. | DBA labor. | None. |
InfluxDB® is a trademark registered by InfluxData, which is not affiliated with, and does not endorse, TSDB for InfluxDB®.
该文章对您有帮助吗?