DBMS > Apache Impala vs. Google BigQuery vs. H2GIS vs. Microsoft Azure Table Storage vs. Postgres-XL

System Properties Comparison Apache Impala vs. Google BigQuery vs. H2GIS vs. Microsoft Azure Table Storage vs. Postgres-XL

Editorial information provided by DB-Engines

Name

Description

Analytic DBMS for Hadoop

Large scale data warehouse service with append-only tables

Spatial extension of H2

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

Based on PostgreSQL enhanced with MPP and write-scale-out cluster features

Primary database model

Secondary database models

Document store

Relational DBMS

Document store
Spatial DBMS

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

Score	13.77
Rank	#40	Overall
	#24	Relational DBMS

Score	60.38
Rank	#19	Overall
	#13	Relational DBMS

Score	0.00
Rank	#383	Overall
	#7	Spatial DBMS

Score	4.48
Rank	#75	Overall
	#6	Wide column stores

Score	0.49
Rank	#256	Overall
	#117	Relational DBMS

Website

impala.apache.org

cloud.google.com/bigquery

www.h2gis.org

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

www.postgres-xl.org

Technical documentation

impala.apache.org/impala-docs.html

cloud.google.com/bigquery/docs

www.h2gis.org/docs/home

www.postgres-xl.org/documentation

Developer

Apache Software Foundation

Apache top-level project, originally developed by Cloudera

Google

CNRS

Microsoft

Initial release

2013

2010

2013

2012

2014

since 2012, originally named StormDB

Current release

4.1.0, June 2022

10 R1, October 2018

License

Commercial or Open Source

Open Source

Apache Version 2

commercial

Open Source

LGPL 3.0

commercial

Open Source

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

Java

Server operating systems

Linux

hosted

Linux
macOS

Data scheme

yes

schema-free

yes

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

XML type, but no XML query functionality

Secondary indexes

yes

SQL

Support of SQL

SQL-like DML and DDL statements

yes

distributed, parallel query execution

APIs and other access methods

JDBC
ODBC

RESTful HTTP/JSON API

RESTful HTTP API

ADO.NET
JDBC
native C library
ODBC
streaming API for large objects

Supported programming languages

All languages supporting JDBC/ODBC

.Net
Java
JavaScript
Objective-C
PHP
Python
Ruby

Java

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

.Net
C
C++
Delphi
Erlang
Java
JavaScript (Node.js)
Perl
PHP
Python
Tcl

Server-side scripts

Stored procedures

yes

user defined functions and integration of map-reduce

user defined functions

in JavaScript

yes

based on H2

user defined functions

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

Sharding

Implicit feature of the cloud service

horizontal partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

selectable replication factor

yes

based on H2

yes

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

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

Since BigQuery is designed for querying data

ACID

optimistic locking

ACID

MVCC

Concurrency

Support for concurrent manipulation of data

yes

yes, multi-version concurrency control (MVCC)

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

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)

yes

based on H2

Access rights based on private key authentication or shared access signatures

fine grained access rights according to SQL-standard

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.