DBMS > Apache Impala vs. Google BigQuery vs. KeyDB vs. Microsoft Azure Table Storage vs. TinkerGraph

System Properties Comparison Apache Impala vs. Google BigQuery vs. KeyDB vs. Microsoft Azure Table Storage vs. TinkerGraph

Editorial information provided by DB-Engines

Name

Description

Analytic DBMS for Hadoop

Large scale data warehouse service with append-only tables

An ultra-fast, open source Key-value store fully compatible with Redis API, modules, and protocols

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

A lightweight, in-memory graph engine that serves as a reference implementation of the TinkerPop3 API

Primary database model

Secondary database models

Document store

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

Score	12.45
Rank	#40	Overall
	#24	Relational DBMS

Score	58.10
Rank	#19	Overall
	#13	Relational DBMS

Score	0.70
Rank	#229	Overall
	#32	Key-value stores

Score	4.04
Rank	#77	Overall
	#6	Wide column stores

Score	0.13
Rank	#345	Overall
	#35	Graph DBMS

Website

impala.apache.org

cloud.google.com/bigquery

github.com/Snapchat/KeyDB
keydb.dev

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

tinkerpop.apache.org/docs/current/reference/#tinkergraph-gremlin

Technical documentation

impala.apache.org/impala-docs.html

cloud.google.com/bigquery/docs

docs.keydb.dev

Developer

Apache Software Foundation

Apache top-level project, originally developed by Cloudera

Google

EQ Alpha Technology Ltd.

Microsoft

Initial release

2013

2010

2019

2012

2009

Current release

4.1.0, June 2022

License

Commercial or Open Source

Open Source

Apache Version 2

commercial

Open Source

BSD-3

commercial

Open Source

Apache 2.0

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

Java

Server operating systems

Linux

hosted

Linux

hosted

Data scheme

yes

schema-free

Typing

predefined data types such as float or date

yes

partial

Supported data types are strings, hashes, lists, sets and sorted sets, bit arrays, hyperloglogs and geospatial indexes

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

by using the Redis Search module

SQL

Support of SQL

SQL-like DML and DDL statements

yes

APIs and other access methods

JDBC
ODBC

RESTful HTTP/JSON API

Proprietary protocol

RESP - REdis Serialization Protoco

RESTful HTTP API

TinkerPop 3

Supported programming languages

All languages supporting JDBC/ODBC

.Net
Java
JavaScript
Objective-C
PHP
Python
Ruby

C
C#
C++
Clojure
Crystal
D
Dart
Elixir
Erlang
Fancy
Go
Haskell
Haxe
Java
JavaScript (Node.js)
Lisp
Lua
MatLab
Objective-C
OCaml
Pascal
Perl
PHP
Prolog
Pure Data
Python
R
Rebol
Ruby
Rust
Scala
Scheme
Smalltalk
Swift
Tcl
Visual Basic

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

Groovy
Java

Server-side scripts

Stored procedures

yes

user defined functions and integration of map-reduce

user defined functions

in JavaScript

Lua

Triggers

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

Multi-source replication
Source-replica replication

yes

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

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

Eventual Consistency
Strong eventual consistency with CRDTs

Immediate Consistency

none

Foreign keys

Referential integrity

yes

Relationships in graphs

Transaction concepts

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

Since BigQuery is designed for querying data

Optimistic locking, atomic execution of commands blocks and scripts

optimistic locking

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

Configurable mechanisms for persistency via snapshots and/or operations logs

yes

optional

In-memory capabilities

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

yes

User concepts

Access control

Access rights for users, groups and roles

based on Apache Sentry and Kerberos

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

Google Cloud Identity & Access Management (IAM)

simple password-based access control and ACL

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.