DBMS > Amazon Redshift vs. Apache Impala vs. Google Cloud Spanner vs. HarperDB

System Properties Comparison Amazon Redshift vs. Apache Impala vs. Google Cloud Spanner vs. HarperDB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Large scale data warehouse service for use with business intelligence tools

Analytic DBMS for Hadoop

A horizontally scalable, globally consistent, relational database service. It is the externalization of the core Google database that runs the biggest aspects of Google, like Ads and Google Play.

HarperDB takes the "stack" out of "tech stack" by combining an ultra-fast document-style data store, in-memory cache, real-time message broker, and your application components into a single distributed technology.

Primary database model

Relational DBMS

Document store

Secondary database models

Document store

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

Score	15.25
Rank	#38	Overall
	#23	Relational DBMS

Score	10.63
Rank	#40	Overall
	#24	Relational DBMS

Score	2.69
Rank	#101	Overall
	#51	Relational DBMS

Score	0.55
Rank	#243	Overall
	#38	Document stores

Website

aws.amazon.com/redshift

impala.apache.org

cloud.google.com/spanner

www.harperdb.io

Technical documentation

docs.aws.amazon.com/redshift

impala.apache.org/impala-docs.html

cloud.google.com/spanner/docs

docs.harperdb.io/docs

Developer

Amazon (based on PostgreSQL)

Apache Software Foundation

Apache top-level project, originally developed by Cloudera

Google

HarperDB

Initial release

2012

2013

2017

Current release

4.1.0, June 2022

3.1, August 2021

License

Commercial or Open Source

commercial

Open Source

Apache Version 2

commercial

free community edition available

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

Node.js

Server operating systems

hosted

Linux

hosted

Linux
OS X

Data scheme

yes

dynamic schema

Typing

predefined data types such as float or date

yes

JSON data types

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

restricted

yes

SQL

Support of SQL

yes

does not fully support an SQL-standard

SQL-like DML and DDL statements

yes

Query statements complying to ANSI 2011

SQL-like data manipulation statements

APIs and other access methods

JDBC
ODBC

gRPC (using protocol buffers) API
JDBC

At present, JDBC supports read-only queries. No support for DDL or DML statements.
RESTful HTTP API

JDBC
ODBC
React Hooks
RESTful HTTP/JSON API
WebSocket

Supported programming languages

All languages supporting JDBC/ODBC

Go
Java
JavaScript (Node.js)
Python

.Net
C
C#
C++
ColdFusion
D
Dart
Delphi
Erlang
Go
Haskell
Java
JavaScript (Node.js)
Lisp
MatLab
Objective C
Perl
PHP
PowerShell
Prolog
Python
R
Ruby
Rust
Scala
Swift

Server-side scripts

Stored procedures

user defined functions

in Python

yes

user defined functions and integration of map-reduce

Custom Functions

since release 3.1

Triggers

Partitioning methods

Methods for storing different data on different nodes

Sharding

A table resides as a whole on one (or more) nodes in a cluster

Replication methods

Methods for redundantly storing data on multiple nodes

yes

selectable replication factor

Multi-source replication with 3 replicas for regional instances.

yes

the nodes on which a table resides can be defined

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

Immediate Consistency

Eventual Consistency

Immediate Consistency

Foreign keys

Referential integrity

yes

informational only, not enforced by the system

yes

by using interleaved tables, this features focuses more on performance improvements than on referential integrity

Transaction concepts

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

ACID

Strict serializable isolation

Atomic execution of specific operations

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

yes, using LMDB

In-memory capabilities

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

yes

User concepts

Access control

fine grained access rights according to SQL-standard

Access rights for users, groups and roles

based on Apache Sentry and Kerberos

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

Access rights for users and roles

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.