DBMS > Amazon Redshift vs. EsgynDB vs. gStore vs. SAP HANA

System Properties Comparison Amazon Redshift vs. EsgynDB vs. gStore vs. SAP HANA

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

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

A native Graph DBMS to store and maintain very large RDF datasets.

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

Primary database model

Relational DBMS

Graph DBMS
RDF store

Relational DBMS

Secondary database models

Document store
Graph DBMS

with SAP Hana, Enterprise Edition
Spatial DBMS

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

Score	16.88
Rank	#35	Overall
	#22	Relational DBMS

Score	0.25
Rank	#312	Overall
	#138	Relational DBMS

Score	0.14
Rank	#342	Overall
	#34	Graph DBMS
	#16	RDF stores

Score	44.27
Rank	#23	Overall
	#16	Relational DBMS

Website

aws.amazon.com/redshift

www.esgyn.cn

en.gstore.cn

www.sap.com/products/hana.html

Technical documentation

docs.aws.amazon.com/redshift

en.gstore.cn/#/enDocs

help.sap.com/hana

Developer

Amazon (based on PostgreSQL)

Esgyn

SAP

Initial release

2012

2015

2016

2010

Current release

1.2, November 2023

2.0 SPS07 (April 4, 2023), April 2023

License

Commercial or Open Source

commercial

Open Source

BSD

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

C++

Server operating systems

hosted

Linux

Appliance or cloud-service

Data scheme

yes

schema-free and OWL/RDFS-schema support

yes

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.

Secondary indexes

restricted

yes

SQL

Support of SQL

yes

does not fully support an SQL-standard

yes

APIs and other access methods

JDBC
ODBC

ADO.NET
JDBC
ODBC

HTTP API
SPARQL 1.1

JDBC
ODBC

Supported programming languages

All languages supporting JDBC/ODBC

All languages supporting JDBC/ODBC/ADO.Net

C++
Java
JavaScript (Node.js)
PHP
Python

Server-side scripts

Stored procedures

user defined functions

in Python

Java Stored Procedures

yes

SQLScript, R

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

yes

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Multi-source replication between multi datacenters

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

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

yes

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

Users, roles and permissions, Role-Based Access Control (RBAC) supported

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.