DBMS > Apache Impala vs. MySQL vs. QuestDB vs. YottaDB

System Properties Comparison Apache Impala vs. MySQL vs. QuestDB vs. YottaDB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Analytic DBMS for Hadoop

Widely used open source RDBMS

A high performance open source SQL database for time series data

A fast and solid embedded Key-value store

Primary database model

Relational DBMS

Key/Value like access via memcached API

Time Series DBMS

Key-value store

Secondary database models

Document store

Document store
Spatial DBMS

Relational DBMS

using the Octo plugin

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

Score	10.22
Rank	#40	Overall
	#24	Relational DBMS

Score	1017.80
Rank	#2	Overall
	#2	Relational DBMS

Score	2.91
Rank	#92	Overall
	#6	Time Series DBMS

Score	0.20
Rank	#308	Overall
	#43	Key-value stores

Website

Technical documentation

impala.apache.org/impala-docs.html

dev.mysql.com/doc

questdb.io/docs

yottadb.com/resources/documentation

Developer

Apache Software Foundation

Apache top-level project, originally developed by Cloudera

Oracle

since 2010, originally MySQL AB, then Sun

QuestDB Technology Inc

YottaDB, LLC

Initial release

2013

1995

2014

2001

Current release

4.1.0, June 2022

9.0.0, July 2024

License

Commercial or Open Source

Open Source

Apache Version 2

Open Source

GPL version 2. Commercial licenses with extended functionallity are available

Open Source

Apache 2.0

Open Source

AGPL 3.0

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++

C and C++

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

Server operating systems

Linux

FreeBSD
Linux
OS X
Solaris
Windows

Linux
macOS
Windows

Docker
Linux

Data scheme

yes

schema-free via InfluxDB Line Protocol

schema-free

Typing

predefined data types such as float or date

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.

yes

Secondary indexes

yes

SQL

Support of SQL

SQL-like DML and DDL statements

yes

with proprietary extensions

SQL with time-series extensions

by using the Octo plugin

APIs and other access methods

JDBC
ODBC

ADO.NET
JDBC
ODBC
Proprietary native API

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

PostgreSQL wire protocol

using the Octo plugin
Proprietary protocol

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

C
Go
JavaScript (Node.js)
Lua
M
Perl
Python
Rust

Server-side scripts

Stored procedures

yes

user defined functions and integration of map-reduce

yes

proprietary syntax

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

horizontal partitioning, sharding with MySQL Cluster or MySQL Fabric

horizontal partitioning (by timestamps)

Replication methods

Methods for redundantly storing data on multiple nodes

selectable replication factor

Multi-source replication
Source-replica replication

Source-replica replication with eventual consistency

yes

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

not for MyISAM storage engine

Transaction concepts

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

ACID

not for MyISAM storage engine

ACID for single-table writes

optimistic locking

Concurrency

Support for concurrent manipulation of data

yes

table locks or row locks depending on storage engine

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

Access rights for users, groups and roles

based on Apache Sentry and Kerberos

Users with fine-grained authorization concept

no user groups or roles

Users and groups based on OS-security mechanisms

More information provided by the system vendor

News

Time-series and analytical databases walk into a bar
28 October 2024

Monitoring QuestDB with simple curl commands
24 October 2024

QuestDB and Raspberry Pi 5 benchmark, a pocket-sized powerhouse
22 October 2024

The future of fast databases: Lessons from a decade of QuestDB
10 October 2024

QuestDB 8.1.2 - Tabs & Balance
8 October 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.