DBMS > Amazon Redshift vs. EsgynDB vs. Google Cloud Bigtable vs. Hive vs. InterSystems Caché

System Properties Comparison Amazon Redshift vs. EsgynDB vs. Google Cloud Bigtable vs. Hive vs. InterSystems Caché

Editorial information provided by DB-Engines

Name

Caché is a deprecated database engine which is substituted with InterSystems IRIS. It therefore is removed from the DB-Engines Ranking.

Description

Large scale data warehouse service for use with business intelligence tools

Enterprise-class SQL-on-Hadoop solution, powered by Apache Trafodion

Google's NoSQL Big Data database service. It's the same database that powers many core Google services, including Search, Analytics, Maps, and Gmail.

data warehouse software for querying and managing large distributed datasets, built on Hadoop

A multi-model DBMS and application server

Primary database model

Relational DBMS

Key-value store
Wide column store

Relational DBMS

Key-value store
Object oriented DBMS
Relational DBMS

Secondary database models

Document store

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

Score	19.03
Rank	#34	Overall
	#21	Relational DBMS

Score	0.23
Rank	#319	Overall
	#141	Relational DBMS

Score	3.58
Rank	#92	Overall
	#14	Key-value stores
	#8	Wide column stores

Score	62.59
Rank	#18	Overall
	#12	Relational DBMS

Website

aws.amazon.com/redshift

www.esgyn.cn

cloud.google.com/bigtable

hive.apache.org

www.intersystems.com/products/cache

Technical documentation

docs.aws.amazon.com/redshift

cloud.google.com/bigtable/docs

cwiki.apache.org/confluence/display/Hive/Home

docs.intersystems.com

Developer

Amazon (based on PostgreSQL)

Esgyn

Google

Apache Software Foundation

initially developed by Facebook

InterSystems

Initial release

2012

2015

2012

1997

Current release

3.1.3, April 2022

2018.1.4, May 2020

License

Commercial or Open Source

commercial

Open Source

Apache Version 2

commercial

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

Java

Server operating systems

hosted

Linux

hosted

All OS with a Java VM

AIX
HP Open VMS
HP-UX
Linux
OS X
Solaris
Windows

Data scheme

yes

schema-free

yes

depending on used data model

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

Secondary indexes

restricted

yes

SQL

Support of SQL

yes

does not fully support an SQL-standard

yes

SQL-like DML and DDL statements

yes

APIs and other access methods

JDBC
ODBC

ADO.NET
JDBC
ODBC

gRPC (using protocol buffers) API
HappyBase (Python library)
HBase compatible API (Java)

JDBC
ODBC
Thrift

.NET Client API
JDBC
ODBC
RESTful HTTP API

Supported programming languages

All languages supporting JDBC/ODBC

All languages supporting JDBC/ODBC/ADO.Net

C#
C++
Go
Java
JavaScript (Node.js)
Python

C++
Java
PHP
Python

C#
C++
Java

Server-side scripts

Stored procedures

user defined functions

in Python

Java Stored Procedures

yes

user defined functions and integration of map-reduce

yes

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Multi-source replication between multi datacenters

Internal replication in Colossus, and regional replication between two clusters in different zones

selectable replication factor

Source-replica replication

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

Immediate Consistency

Immediate consistency (for a single cluster), Eventual consistency (for two or more replicated clusters)

Eventual Consistency

Immediate Consistency

Foreign keys

Referential integrity

yes

informational only, not enforced by the system

yes

Transaction concepts

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

ACID

Atomic single-row operations

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

fine grained access rights according to SQL-standard

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

Access rights for users, groups 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.