DBMS > Apache Impala vs. Google BigQuery vs. Google Cloud Datastore vs. Heroic vs. SAP HANA

System Properties Comparison Apache Impala vs. Google BigQuery vs. Google Cloud Datastore vs. Heroic vs. SAP HANA

Editorial information provided by DB-Engines

Name

Description

Analytic DBMS for Hadoop

Large scale data warehouse service with append-only tables

Automatically scaling NoSQL Database as a Service (DBaaS) on the Google Cloud Platform

Time Series DBMS built at Spotify based on Cassandra or Google Cloud Bigtable, and ElasticSearch

In-memory, column based data store. Available as appliance or cloud service

Primary database model

Secondary database models

Document store

Document store
Graph DBMS

with SAP Hana, Enterprise Edition
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	4.47
Rank	#76	Overall
	#12	Document stores

Score	0.51
Rank	#255	Overall
	#21	Time Series DBMS

Score	44.69
Rank	#22	Overall
	#16	Relational DBMS

Website

impala.apache.org

cloud.google.com/bigquery

cloud.google.com/datastore

github.com/spotify/heroic

www.sap.com/products/hana.html

Technical documentation

impala.apache.org/impala-docs.html

cloud.google.com/bigquery/docs

cloud.google.com/datastore/docs

spotify.github.io/heroic

help.sap.com/hana

Developer

Apache Software Foundation

Apache top-level project, originally developed by Cloudera

Google

Spotify

SAP

Initial release

2013

2010

2008

2014

2010

Current release

4.1.0, June 2022

2.0 SPS07 (April 4, 2023), April 2023

License

Commercial or Open Source

Open Source

Apache Version 2

commercial

Open Source

Apache 2.0

commercial

Cloud-based only

Only available as a cloud service

yes

also available as a cloud based service

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

Appliance or cloud-service

Data scheme

yes

schema-free

yes

Typing

predefined data types such as float or date

yes

yes, details here

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

via Elasticsearch

yes

SQL

Support of SQL

SQL-like DML and DDL statements

yes

SQL-like query language (GQL)

yes

APIs and other access methods

JDBC
ODBC

RESTful HTTP/JSON API

gRPC (using protocol buffers) API
RESTful HTTP/JSON API

HQL (Heroic Query Language, a JSON-based language)
HTTP API

JDBC
ODBC

Supported programming languages

All languages supporting JDBC/ODBC

.Net
Java
JavaScript
Objective-C
PHP
Python
Ruby

.Net
Go
Java
JavaScript (Node.js)
PHP
Python
Ruby

Server-side scripts

Stored procedures

yes

user defined functions and integration of map-reduce

user defined functions

in JavaScript

using Google App Engine

SQLScript, R

Triggers

Callbacks using the Google Apps Engine

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

Sharding

yes

Replication methods

Methods for redundantly storing data on multiple nodes

selectable replication factor

Multi-source replication using Paxos

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

query execution via MapReduce

yes

using Google Cloud Dataflow

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency

Immediate Consistency

Immediate Consistency or Eventual Consistency depending on type of query and configuration

Strong Consistency is default for entity lookups and queries within an Entity Group (but can instead be made eventually consistent). Other queries are always eventual consistent.

Eventual Consistency
Immediate Consistency

Immediate Consistency

Foreign keys

Referential integrity

yes

via ReferenceProperties or Ancestor paths

yes

Transaction concepts

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

Since BigQuery is designed for querying data

ACID

Serializable Isolation within Transactions, Read Committed outside of Transactions

ACID

Concurrency

Support for concurrent manipulation of data

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)

Access rights for users, groups and roles based on Google Cloud Identity and Access Management (IAM)

yes

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.