Apache IoTDB vs UnitDB
Apache IoTDB
iotdb.apache.orgUnitDB
github.comSide by side
| Figure | Apache IoTDB | UnitDB |
|---|---|---|
| Price from | Free | — |
| Free plan | Yes | — |
| Free trial | — | — |
| Open source | Yes | — |
| Web | Yes | — |
| Windows | Yes | — |
| macOS | Yes | — |
| Linux | Yes | Yes |
| API | Yes | Yes |
| Self-hosted | Yes | Yes |
| Plans published | 2 | 0 |
| Spec score · Time-Series Databases | 9.1 (#2) | 6.9 (#34) |
| Integrations | Documented integrations include Telegraf, NiFi, Kafka, Flink, Spark, Zeppelin, Grafana, DataEase, DBeaver and ThingsBoard. | The maker lists supported Go and Flutter/Dart client libraries for connecting to a UnitDB server. |
| Product | Apache IoTDB is an industrial IoT time-series database for collecting, storing, managing, and analyzing IoT time-series data with edge-cloud collaboration. | UnitDB is an open-source time-series database and publish-subscribe messaging server aimed at IoT and real-time connected devices. |
Plans
In their own words
Apache IoTDB
Apache IoTDB is an open-source industrial IoT time-series database for collecting, storing, managing, and analyzing device data across edge and cloud deployments. The project describes high-speed writes for millions of networked devices alongside fast reads. Query features include aligning time across devices and sensors, time-series computation, and aggregation by time dimensions. Ingestion options include IoTDB-SQL, JDBC, Java, C++, Python, and Go native APIs, REST, MQTT, CSV, and TsFile. Named analysis ecosystem examples include Hadoop, Spark, Flink, and Grafana. Deployment options include cloud installation, a desktop terminal tool, and synchronization between cloud and on-premise machines. The REST service is disabled by default and uses Basic Authentication except for the health check endpoint. Data and cluster permissions can be managed through users, roles, and privileges. The homepage states disk storage can cost less than $0.23 per GB. The project lists energy, aerospace, transportation, steel, and other IoT scenarios. Its JDBC documentation cautions that insert operations may not provide high-performance writing and recommends the Java Native API for Java applications.