DBMS > BoltDB vs. Heroic vs. QuestDB vs. SQLite vs. TDengine

System Properties Comparison BoltDB vs. Heroic vs. QuestDB vs. SQLite vs. TDengine

Editorial information provided by DB-Engines

Name

Description

An embedded key-value store for Go.

Time Series DBMS built at Spotify based on Cassandra or Google Cloud Bigtable, and ElasticSearch

A high performance open source SQL database for time series data

Widely used embeddable, in-process RDBMS

Time Series DBMS and big data platform

Primary database model

Secondary database models

Relational DBMS

DB-Engines Ranking measures the popularity of database management systems
Trend Chart

Score	0.74
Rank	#220	Overall
	#31	Key-value stores

Score	0.51
Rank	#255	Overall
	#21	Time Series DBMS

Score	2.52
Rank	#109	Overall
	#9	Time Series DBMS

Score	114.32
Rank	#10	Overall
	#7	Relational DBMS

Score	2.60
Rank	#107	Overall
	#8	Time Series DBMS

Website

github.com/boltdb/bolt

github.com/spotify/heroic

questdb.io

www.sqlite.org

github.com/taosdata/TDengine
tdengine.com

Technical documentation

spotify.github.io/heroic

questdb.io/docs

www.sqlite.org/docs.html

docs.tdengine.com

Developer

Spotify

QuestDB Technology Inc

Dwayne Richard Hipp

TDEngine, previously Taos Data

Initial release

2013

2014

2000

2019

Current release

3.45.3 (15 April 2024), April 2024

3.0, August 2022

License

Commercial or Open Source

Open Source

MIT License

Open Source

Apache 2.0

Open Source

Apache 2.0

Open Source

Public Domain

Open Source

AGPL V3, also commercial editions available

Cloud-based only

Only available as a cloud service

DBaaS offerings (sponsored links)

Database as a Service

Providers of DBaaS offerings, please contact us to be listed.

Implementation language

Java

Java (Zero-GC), C++, Rust

Server operating systems

BSD
Linux
OS X
Solaris
Windows

Linux
macOS
Windows

server-less

Linux
Windows

Data scheme

schema-free

yes

schema-free via InfluxDB Line Protocol

yes

dynamic column types

yes

Typing

predefined data types such as float or date

yes

not rigid because of 'dynamic typing' concept.

yes

XML support

Some form of processing data in XML format, e.g. support for XML data structures, and/or support for XPath, XQuery or XSLT.

Secondary indexes

yes

via Elasticsearch

yes

SQL

Support of SQL

SQL with time-series extensions

yes

SQL-92 is not fully supported

Standard SQL with extensions for time-series applications

APIs and other access methods

HQL (Heroic Query Language, a JSON-based language)
HTTP API

HTTP REST
InfluxDB Line Protocol (TCP/UDP)
JDBC
PostgreSQL wire protocol

ADO.NET

inofficial driver
JDBC

inofficial driver
ODBC

inofficial driver

JDBC
RESTful HTTP API

Supported programming languages

PostgreSQL driver
C++
Go
Java
JavaScript (Node.js)
Python
Rust

over HTTP

Actionscript
Ada
Basic
C
C#
C++
D
Delphi
Forth
Fortran
Haskell
Java
JavaScript
Lisp
Lua
MatLab
Objective-C
OCaml
Perl
PHP
PL/SQL
Python
R
Ruby
Scala
Scheme
Smalltalk
Tcl

C
C#
C++
Go
Java
JavaScript (Node.js)
PHP
Python
Rust

Server-side scripts

Stored procedures

Triggers

yes

yes, via alarm monitoring

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

horizontal partitioning (by timestamps)

none

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

none

yes

Source-replica replication with eventual consistency

none

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

none

Eventual Consistency
Immediate Consistency

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

Support to ensure data integrity after non-atomic manipulations of data

yes

ACID for single-table writes

ACID

Concurrency

Support for concurrent manipulation of data

yes

via file-system locks

yes

Durability

Support for making data persistent

yes

In-memory capabilities

Is there an option to define some or all structures to be held in-memory only.

yes

through memory mapped files

yes

User concepts

Access control

yes

More information provided by the system vendor

Specific characteristics

Relational model with native time series support Column-based storage and time partitioned...
» more

TDengine™ is a next generation data historian purpose-built for Industry 4.0 and...
» more

Competitive advantages

High ingestion throughput: peak of 4M rows/sec (TSBS Benchmark) Code optimizations...
» more

High Performance at any Scale: TDengine is purpose-built for handling massive industrial...
» more

Typical application scenarios

Financial tick data Industrial IoT Application Metrics Monitoring
» more

TDengine is designed for Industrial IoT scenarios, including: Manufacturing Connected...
» more

Key customers

Banks & Hedge funds, Yahoo, OKX, Airbus, Aquis Exchange, Net App, Cloudera, Airtel,...
» more

Market metrics

TDengine has garnered over 22,500 stars on GitHub and is used in over 50 countries...
» more

Licensing and pricing models

Open source Apache 2.0 QuestDB Enterprise QuestDB Cloud
» more

TDengine OSS is an open source, cloud native time series database. It includes built-in...
» more

News

QuestDB and Raspberry Pi 5 benchmark, a pocket-sized powerhouse
8 May 2024

Build your own resource monitor with QuestDB and Grafana
6 May 2024

Does "vpmovzxbd" Scare You? Here's Why it Doesn't Have To
12 April 2024

Create an ADS-B flight radar with QuestDB and a Raspberry Pi
8 April 2024

Build a temperature IoT sensor with Raspberry Pi Pico & QuestDB
5 April 2024

Can Typical Time-Series Databases Replace Data Historians?
8 May 2024

TDengine 3.3.0.0 Release Notes
7 May 2024

How to Unlock Value from Industrial Data with AI and ML Technology
6 May 2024

Compare InfluxDB vs. TDengine
19 April 2024

Why We Need the Next Generation Data Historian
15 April 2024

We invite representatives of system vendors to contact us for updating and extending the system information,
and for displaying vendor-provided information such as key customers, competitive advantages and market metrics.