DBMS > Apache Impala vs. Dolt vs. Google BigQuery vs. Microsoft Azure Table Storage vs. XTDB

System Properties Comparison Apache Impala vs. Dolt vs. Google BigQuery vs. Microsoft Azure Table Storage vs. XTDB

Editorial information provided by DB-Engines

Name

Description

Analytic DBMS for Hadoop

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

Large scale data warehouse service with append-only tables

A Wide Column Store for rapid development using massive semi-structured datasets

A general purpose database with bitemporal SQL and Datalog and graph queries

Primary database model

Relational DBMS

Wide column store

Document store

Secondary database models

Document store

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

Score	13.77
Rank	#40	Overall
	#24	Relational DBMS

Score	0.96
Rank	#193	Overall
	#90	Relational DBMS

Score	60.38
Rank	#19	Overall
	#13	Relational DBMS

Score	4.48
Rank	#75	Overall
	#6	Wide column stores

Score	0.11
Rank	#343	Overall
	#46	Document stores

Website

impala.apache.org

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

cloud.google.com/bigquery

azure.microsoft.com/en-us/services/storage/tables

github.com/xtdb/xtdb
www.xtdb.com

Technical documentation

impala.apache.org/impala-docs.html

docs.dolthub.com

cloud.google.com/bigquery/docs

www.xtdb.com/docs

Developer

Apache Software Foundation

Apache top-level project, originally developed by Cloudera

DoltHub Inc

Google

Microsoft

Juxt Ltd.

Initial release

2013

2018

2010

2012

2019

Current release

4.1.0, June 2022

1.19, September 2021

License

Commercial or Open Source

Open Source

Apache Version 2

Open Source

Apache Version 2.0

commercial

Open Source

MIT License

Cloud-based only

Only available as a cloud service

yes

DBaaS offerings (sponsored links)

Database as a Service

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

Implementation language

C++

Clojure

Server operating systems

Linux

Linux
macOS
Windows

hosted

All OS with a Java 8 (and higher) VM
Linux

Data scheme

yes

schema-free

Typing

predefined data types such as float or date

yes

yes, extensible-data-notation format

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

limited SQL, making use of Apache Calcite

APIs and other access methods

JDBC
ODBC

CLI Client
HTTP REST

RESTful HTTP/JSON API

RESTful HTTP API

HTTP REST
JDBC

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

.Net
Java
JavaScript
Objective-C
PHP
Python
Ruby

.Net
C#
C++
Java
JavaScript (Node.js)
PHP
Python
Ruby

Clojure
Java

Server-side scripts

Stored procedures

yes

user defined functions and integration of map-reduce

yes

currently in alpha release

user defined functions

in JavaScript

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

Sharding

Implicit feature of the cloud service

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.

yes

implicit feature of the cloud service. Replication either local, cross-facility or geo-redundant.

yes, each node contains all data

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

Since BigQuery is designed for querying data

optimistic locking

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

yes, flexibel persistency by using storage technologies like Apache Kafka, RocksDB or LMDB

In-memory capabilities

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

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

Access privileges (owner, writer, reader) on dataset, table or view level

Google Cloud Identity & Access Management (IAM)

Access rights based on private key authentication or shared access signatures

More information provided by the system vendor

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.