DBMS > Alibaba Cloud MaxCompute vs. Amazon DynamoDB vs. Newts vs. Tarantool

System Properties Comparison Alibaba Cloud MaxCompute vs. Amazon DynamoDB vs. Newts vs. Tarantool

Please select another system to include it in the comparison.

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

Hosted, scalable database service by Amazon with the data stored in Amazons cloud

Time Series DBMS based on Cassandra

In-memory computing platform with a flexible data schema for efficiently building high-performance applications

Primary database model

Relational DBMS

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

Document store
Key-value store

Time Series DBMS

Document store
Key-value store
Relational DBMS

Secondary database models

Spatial DBMS

with Tarantool/GIS extension

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

Score	0.78
Rank	#221	Overall
	#102	Relational DBMS

Score	77.57
Rank	#16	Overall
	#2	Document stores
	#2	Key-value stores

Score	0.00
Rank	#396	Overall
	#42	Time Series DBMS

Score	1.67
Rank	#150	Overall
	#25	Document stores
	#25	Key-value stores
	#69	Relational DBMS

Website

www.alibabacloud.com/product/maxcompute

aws.amazon.com/dynamodb

opennms.github.io/newts

www.tarantool.io

Technical documentation

www.alibabacloud.com/help/en/maxcompute

docs.aws.amazon.com/dynamodb

github.com/OpenNMS/newts/wiki

www.tarantool.io/en/doc

Developer

Alibaba

Amazon

OpenNMS Group

Initial release

2016

2012

2014

2008

Current release

2.10.0, May 2022

License

Commercial or Open Source

commercial

free tier for a limited amount of database operations

Open Source

Apache 2.0

Open Source

BSD-2, source-available extensions (modules), commercial licenses for Tarantool Enterprise

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 and C++

Server operating systems

hosted

Linux
OS X
Windows

BSD
Linux
macOS

Data scheme

yes

schema-free

Flexible data schema: relational definition for tables with ability to store json-like documents in columns

Typing

predefined data types such as float or date

yes

string, double, decimal, uuid, integer, blob, boolean, datetime

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

yes

SQL

Support of SQL

SQL-like query language

Full-featured ANSI SQL support

APIs and other access methods

Fluentd
Flume
MaxCompute Console

RESTful HTTP API

HTTP REST
Java API

Open binary protocol

Supported programming languages

Java

.Net
ColdFusion
Erlang
Groovy
Java
JavaScript
Perl
PHP
Python
Ruby

Java

C
C#
C++
Erlang
Go
Java
JavaScript
Lua
Perl
PHP
Python
Rust

Server-side scripts

Stored procedures

user defined functions

in Java

Lua, C and SQL stored procedures

Triggers

yes

by integration with AWS Lambda

yes, before/after data modification events, on replication events, client session events

Partitioning methods

Methods for storing different data on different nodes

Sharding

Implicit feature of the cloud service

Sharding

based on Cassandra

Sharding, partitioned with virtual buckets by user defined affinity key. Live resharding for scale up and scale down without maintenance downtime.

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Implicit feature of the cloud service

yes

selectable replication factor

based on Cassandra

Asynchronous replication with multi-master option
Configurable replication topology (full-mesh, chain, star)
Synchronous quorum replication (with Raft)

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

may be implemented via Amazon Elastic MapReduce (Amazon EMR)

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency
Immediate Consistency

can be specified for read operations

Eventual Consistency

based on Cassandra
Immediate Consistency

based on Cassandra

Casual consistency across sharding partitions
Eventual consistency within replicaset partition

when using asyncronous replication
Immediate Consistency within single instance
Sequential consistency including linearizable read within replicaset partition

when using Raft

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

ACID across one or more tables within a single AWS account and region

ACID, with serializable isolation and linearizable read (within partition); Configurable MVCC (within partition); No cross-shard distributed transactions

Concurrency

Support for concurrent manipulation of data

yes

yes, cooperative multitasking

Durability

Support for making data persistent

yes

yes, write ahead logging

In-memory capabilities

Is there an option to define some or all structures to be held in-memory only.

yes, full featured in-memory storage engine with persistence

User concepts

Access control

Access rights for users and roles

Access rights for users and roles can be defined via the AWS Identity and Access Management (IAM)

Access Control Lists
Mutual TLS authentication for Tarantol Enterprise
Password based authentication
Role-based access control (RBAC) and LDAP for Tarantol Enterprise
Users 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.