DBMS > Apache Impala vs. Dolt vs. QuestDB vs. SQLite

System Properties Comparison Apache Impala vs. Dolt vs. QuestDB vs. SQLite

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Analytic DBMS for Hadoop

A MySQL compatible DBMS with Git-like versioning of data and schema

A high performance open source SQL database for time series data

Widely used embeddable, in-process RDBMS

Primary database model

Relational DBMS

Time Series DBMS

Relational DBMS

Secondary database models

Document store

Relational DBMS

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

Score	12.45
Rank	#40	Overall
	#24	Relational DBMS

Score	1.02
Rank	#191	Overall
	#89	Relational DBMS

Score	2.70
Rank	#105	Overall
	#8	Time Series DBMS

Score	111.41
Rank	#10	Overall
	#7	Relational DBMS

Website

impala.apache.org

github.com/dolthub/dolt
www.dolthub.com

questdb.io

www.sqlite.org

Technical documentation

impala.apache.org/impala-docs.html

docs.dolthub.com

questdb.io/docs

www.sqlite.org/docs.html

Developer

Apache Software Foundation

Apache top-level project, originally developed by Cloudera

DoltHub Inc

QuestDB Technology Inc

Dwayne Richard Hipp

Initial release

2013

2018

2014

2000

Current release

4.1.0, June 2022

3.46.0 (23 May 2024), May 2024

License

Commercial or Open Source

Open Source

Apache Version 2

Open Source

Apache Version 2.0

Open Source

Apache 2.0

Open Source

Public Domain

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

C++

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

Server operating systems

Linux

Linux
macOS
Windows

server-less

Data scheme

yes

schema-free via InfluxDB Line Protocol

yes

dynamic column types

Typing

predefined data types such as float or date

yes

not rigid because of 'dynamic typing' concept.

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

SQL

Support of SQL

SQL-like DML and DDL statements

yes

SQL with time-series extensions

yes

SQL-92 is not fully supported

APIs and other access methods

JDBC
ODBC

CLI Client
HTTP REST

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

ADO.NET

inofficial driver
JDBC

inofficial driver
ODBC

inofficial driver

Supported programming languages

All languages supporting JDBC/ODBC

Ada
C
C#
C++
D
Delphi
Eiffel
Erlang
Haskell
Java
JavaScript (Node.js)
Objective-C
OCaml
Perl
PHP
Python
Ruby
Scheme
Tcl

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

Server-side scripts

Stored procedures

yes

user defined functions and integration of map-reduce

yes

currently in alpha release

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

horizontal partitioning (by timestamps)

none

Replication methods

Methods for redundantly storing data on multiple nodes

selectable replication factor

A database can be cloned to multiple locations and be used there in isolation. Data/schema changes can be pushed/pulled explicitly between locations.

Source-replica replication with eventual consistency

none

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

query execution via MapReduce

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

ACID for single-table writes

ACID

Concurrency

Support for concurrent manipulation of data

yes

via file-system locks

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

Access rights for users, groups and roles

based on Apache Sentry and Kerberos

Only one user is configurable, and must be specified in the config file at startup

More information provided by the system vendor

Specific characteristics

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

Competitive advantages

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

Typical application scenarios

Financial tick data Industrial IoT Application Metrics Monitoring
» more

Key customers

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

Licensing and pricing models

Open source Apache 2.0 QuestDB Enterprise QuestDB Cloud
» more

News

QuestDB 8.0: Major Release
23 May 2024

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

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.