DBMS > Amazon Redshift vs. BigchainDB vs. Google Cloud Datastore vs. HarperDB

System Properties Comparison Amazon Redshift vs. BigchainDB vs. Google Cloud Datastore 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

BigchainDB is scalable blockchain database offering decentralization, immutability and native assets

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

Ultra-low latency distributed database with an intuitive REST API supporting NoSQL and SQL (including joins). Deployment of functions and databases simultaneously with a consolidated node-level architecture.

Primary database model

Relational DBMS

Document store

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

Score	17.94
Rank	#34	Overall
	#21	Relational DBMS

Score	0.79
Rank	#212	Overall
	#36	Document stores

Score	4.47
Rank	#76	Overall
	#12	Document stores

Score	0.55
Rank	#248	Overall
	#38	Document stores

Website

aws.amazon.com/redshift

www.bigchaindb.com

cloud.google.com/datastore

www.harperdb.io

Technical documentation

docs.aws.amazon.com/redshift

bigchaindb.readthedocs.io/en/latest

cloud.google.com/datastore/docs

docs.harperdb.io/docs

Developer

Amazon (based on PostgreSQL)

Google

HarperDB

Initial release

2012

2016

2008

2017

Current release

3.1, August 2021

License

Commercial or Open Source

commercial

Open Source

AGPL v3

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

Python

Node.js

Server operating systems

hosted

Linux

hosted

Linux
OS X

Data scheme

yes

schema-free

dynamic schema

Typing

predefined data types such as float or date

yes

yes, details here

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 query language (GQL)

SQL-like data manipulation statements

APIs and other access methods

JDBC
ODBC

CLI Client
RESTful HTTP API

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

JDBC
ODBC
React Hooks
RESTful HTTP/JSON API
WebSocket

Supported programming languages

All languages supporting JDBC/ODBC

Go
Haskell
Java
JavaScript
Python
Ruby

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

.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

using Google App Engine

Custom Functions

since release 3.1

Triggers

Callbacks using the Google Apps Engine

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 using Paxos

yes

the nodes on which a table resides can be defined

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

using Google Cloud Dataflow

Consistency concepts

Methods to ensure consistency in a distributed system

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.

Immediate Consistency

Foreign keys

Referential integrity

yes

informational only, not enforced by the system

yes

via ReferenceProperties or Ancestor paths

Transaction concepts

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

ACID

Serializable Isolation within Transactions, Read Committed outside of Transactions

Atomic execution of specific operations

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

yes,with MongoDB ord RethinkDB

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

yes

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.