DBMS > Alibaba Cloud MaxCompute vs. Amazon Redshift vs. Dolt vs. Hazelcast vs. Tkrzw

System Properties Comparison Alibaba Cloud MaxCompute vs. Amazon Redshift vs. Dolt vs. Hazelcast vs. Tkrzw

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

A MySQL compatible DBMS with Git-like versioning of data and schema

A widely adopted in-memory data grid

A concept of libraries, allowing an application program to store and query key-value pairs in a file. Successor of Tokyo Cabinet and Kyoto Cabinet

Primary database model

Relational DBMS

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

Relational DBMS

Key-value store

Secondary database models

Document store

JSON support with IMDG 3.12

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

Score	0.84
Rank	#209	Overall
	#98	Relational DBMS

Score	16.88
Rank	#35	Overall
	#22	Relational DBMS

Score	1.02
Rank	#191	Overall
	#89	Relational DBMS

Score	5.46
Rank	#61	Overall
	#7	Key-value stores

Score	0.07
Rank	#372	Overall
	#57	Key-value stores

Website

www.alibabacloud.com/product/maxcompute

aws.amazon.com/redshift

github.com/dolthub/dolt
www.dolthub.com

hazelcast.com

dbmx.net/tkrzw

Technical documentation

www.alibabacloud.com/help/en/maxcompute

docs.aws.amazon.com/redshift

docs.dolthub.com

hazelcast.org/imdg/docs

Developer

Alibaba

Amazon (based on PostgreSQL)

DoltHub Inc

Hazelcast

Mikio Hirabayashi

Initial release

2016

2012

2018

2008

2020

Current release

5.3.6, November 2023

0.9.3, August 2020

License

Commercial or Open Source

commercial

Open Source

Apache Version 2.0

Open Source

Apache Version 2; commercial licenses available

Open Source

Apache Version 2.0

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

Java

C++

Server operating systems

hosted

Linux
macOS
Windows

All OS with a Java VM

Linux
macOS

Data scheme

yes

schema-free

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

the object must implement a serialization strategy

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

APIs and other access methods

Fluentd
Flume
MaxCompute Console

JDBC
ODBC

CLI Client
HTTP REST

JCache
JPA
Memcached protocol
RESTful HTTP API

Supported programming languages

Java

All languages supporting JDBC/ODBC

Ada
C
C#
C++
D
Delphi
Eiffel
Erlang
Haskell
Java
JavaScript (Node.js)
Objective-C
OCaml
Perl
PHP
Python
Ruby
Scheme
Tcl

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

C++
Java
Python
Ruby

Server-side scripts

Stored procedures

user defined functions

in Java

user defined functions

in Python

yes

currently in alpha release

yes

Event Listeners, Executor Services

Triggers

yes

Events

Partitioning methods

Methods for storing different data on different nodes

Sharding

Implicit feature of the cloud service

Sharding

none

Sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Implicit feature of the cloud service

yes

A database can be cloned to multiple locations and be used there in isolation. Data/schema changes can be pushed/pulled explicitly between locations.

yes

Replicated Map

none

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Immediate Consistency or Eventual Consistency selectable by user

Raft Consensus Algorithm

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

one or two-phase-commit; repeatable reads; read commited

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

using specific database classes

User concepts

Access control

Access rights for users and roles

fine grained access rights according to SQL-standard

Only one user is configurable, and must be specified in the config file at startup

Role-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.