DBMS > Amazon Redshift vs. GBase vs. Google Cloud Datastore vs. HBase

System Properties Comparison Amazon Redshift vs. GBase vs. Google Cloud Datastore vs. HBase

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

Widely used RDBMS in China, including analytical, transactional, distributed transactional, and cloud-native data warehousing.

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

Wide-column store based on Apache Hadoop and on concepts of BigTable

Primary database model

Relational DBMS

Document store

Wide column store

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

Score	17.94
Rank	#34	Overall
	#21	Relational DBMS

Score	1.07
Rank	#185	Overall
	#86	Relational DBMS

Score	4.47
Rank	#76	Overall
	#12	Document stores

Score	30.50
Rank	#26	Overall
	#2	Wide column stores

Website

aws.amazon.com/redshift

www.gbase.cn

cloud.google.com/datastore

hbase.apache.org

Technical documentation

docs.aws.amazon.com/redshift

cloud.google.com/datastore/docs

hbase.apache.org/book.html

Developer

Amazon (based on PostgreSQL)

General Data Technology Co., Ltd.

Google

Apache Software Foundation

Apache top-level project, originally developed by Powerset

Initial release

2012

2004

2008

Current release

GBase 8a, GBase 8s, GBase 8c

2.3.4, January 2021

License

Commercial or Open Source

commercial

Open Source

Apache version 2

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, Python

Java

Server operating systems

hosted

Linux

hosted

Linux
Unix
Windows

using Cygwin

Data scheme

yes

schema-free

schema-free, schema definition possible

Typing

predefined data types such as float or date

yes

yes, details here

options to bring your own types, AVRO

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

Secondary indexes

restricted

yes

SQL

Support of SQL

yes

does not fully support an SQL-standard

Standard with numerous extensions

SQL-like query language (GQL)

APIs and other access methods

JDBC
ODBC

ADO.NET
C API
JDBC
ODBC

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

Java API
RESTful HTTP API
Thrift

Supported programming languages

All languages supporting JDBC/ODBC

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

C
C#
C++
Groovy
Java
PHP
Python
Scala

Server-side scripts

Stored procedures

user defined functions

in Python

user defined functions

using Google App Engine

yes

Coprocessors in Java

Triggers

yes

Callbacks using the Google Apps Engine

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

horizontal partitioning (by range, list and hash) and vertical partitioning

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Multi-source replication using Paxos

Multi-source replication
Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

using Google Cloud Dataflow

yes

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 or Eventual 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

Single row ACID (across millions of columns)

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

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 Control Lists (ACL) for RBAC, integration with Apache Ranger for RBAC & ABAC

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.