DBMS > Alibaba Cloud MaxCompute vs. Amazon Redshift vs. EsgynDB vs. Geode vs. Sequoiadb

System Properties Comparison Alibaba Cloud MaxCompute vs. Amazon Redshift vs. EsgynDB vs. Geode vs. Sequoiadb

Editorial information provided by DB-Engines

Name

Description

MaxCompute (previously known as ODPS) is a general purpose, fully managed, multi-tenancy data processing platform for large-scale data warehousing

Large scale data warehouse service for use with business intelligence tools

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

Geode is a distributed data container, pooling memory, CPU, network resources, and optionally local disk across multiple processes

NewSQL database with distributed OLTP and SQL

Primary database model

Relational DBMS

a graph-processing framework is available with the graphs being stored in tables

Relational DBMS

Key-value store

Document store
Relational DBMS

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

Score	0.77
Rank	#214	Overall
	#98	Relational DBMS

Score	17.94
Rank	#34	Overall
	#21	Relational DBMS

Score	0.16
Rank	#329	Overall
	#146	Relational DBMS

Score	1.92
Rank	#131	Overall
	#23	Key-value stores

Score	0.45
Rank	#261	Overall
	#41	Document stores
	#122	Relational DBMS

Website

www.alibabacloud.com/product/maxcompute

aws.amazon.com/redshift

www.esgyn.cn

geode.apache.org

www.sequoiadb.com

Technical documentation

www.alibabacloud.com/help/en/maxcompute

docs.aws.amazon.com/redshift

geode.apache.org/docs

www.sequoiadb.com/en/index.php?m=Files&a=index

Developer

Alibaba

Amazon (based on PostgreSQL)

Esgyn

Originally developed by Gemstone. They outsourced the project to Apache in 2015 but still deliver a commercial version as Gemfire.

Sequoiadb Ltd.

Initial release

2016

2012

2015

2002

2013

Current release

1.1, February 2017

License

Commercial or Open Source

commercial

Open Source

Apache Version 2; commercial licenses available as Gemfire

Open Source

Server: AGPL; Client: Apache V2

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

C++

Server operating systems

hosted

Linux

All OS with a Java VM

the JDK (8 or later) is also required

Linux

Data scheme

yes

schema-free

Typing

predefined data types such as float or date

yes

oid, date, timestamp, binary, regex

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

SQL-like query language

yes

does not fully support an SQL-standard

yes

SQL-like query language (OQL)

SQL-like query language

APIs and other access methods

Fluentd
Flume
MaxCompute Console

JDBC
ODBC

ADO.NET
JDBC
ODBC

Java Client API
Memcached protocol
RESTful HTTP API

proprietary protocol using JSON

Supported programming languages

Java

All languages supporting JDBC/ODBC

All languages supporting JDBC/ODBC/ADO.Net

.Net
All JVM based languages
C++
Groovy
Java
Scala

.Net
C++
Java
PHP
Python

Server-side scripts

Stored procedures

user defined functions

in Java

user defined functions

in Python

Java Stored Procedures

user defined functions

JavaScript

Triggers

yes

Cache Event Listeners

Partitioning methods

Methods for storing different data on different nodes

Sharding

Implicit feature of the cloud service

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Implicit feature of the cloud service

yes

Multi-source replication between multi datacenters

Multi-source replication

Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual 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, on a single node

Document is locked during a transaction

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

Access rights for users and roles

fine grained access rights according to SQL-standard

Access rights per client and object definable

simple password-based access control

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.