DBMS > Alibaba Cloud MaxCompute vs. Amazon DynamoDB vs. BoltDB vs. Coveo vs. Vitess

System Properties Comparison Alibaba Cloud MaxCompute vs. Amazon DynamoDB vs. BoltDB vs. Coveo vs. Vitess

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

An embedded key-value store for Go.

AI-powered hosted search, recommendation and personalization platform providing tools for both low-code and full-code development

Scalable, distributed, cloud-native DBMS, extending MySQL

Primary database model

Relational DBMS

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

Document store
Key-value store

Key-value store

Search engine

Relational DBMS

Secondary database models

Document store
Spatial DBMS

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

Score	0.84
Rank	#209	Overall
	#98	Relational DBMS

Score	74.45
Rank	#17	Overall
	#3	Document stores
	#2	Key-value stores

Score	0.80
Rank	#215	Overall
	#31	Key-value stores

Score	2.11
Rank	#118	Overall
	#11	Search engines

Score	0.88
Rank	#203	Overall
	#95	Relational DBMS

Website

www.alibabacloud.com/product/maxcompute

aws.amazon.com/dynamodb

github.com/boltdb/bolt

www.coveo.com

vitess.io

Technical documentation

www.alibabacloud.com/help/en/maxcompute

docs.aws.amazon.com/dynamodb

docs.coveo.com

vitess.io/docs

Developer

Alibaba

Amazon

Coveo

The Linux Foundation, PlanetScale

Initial release

2016

2012

2013

2012

2013

Current release

15.0.2, December 2022

License

Commercial or Open Source

commercial

free tier for a limited amount of database operations

Open Source

MIT License

commercial

Open Source

Apache Version 2.0, commercial licenses available

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

Server operating systems

hosted

BSD
Linux
OS X
Solaris
Windows

hosted

Docker
Linux
macOS

Data scheme

yes

schema-free

hybrid - fields need to be configured prior to indexing, but relationships can be exploited at query time without pre-configuration

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

yes

SQL

Support of SQL

SQL-like query language

yes

with proprietary extensions

APIs and other access methods

Fluentd
Flume
MaxCompute Console

RESTful HTTP API

ADO.NET
JDBC
MySQL protocol
ODBC

Supported programming languages

Java

.Net
ColdFusion
Erlang
Groovy
Java
JavaScript
Perl
PHP
Python
Ruby

C#
Java
JavaScript
Python

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

Server-side scripts

Stored procedures

user defined functions

in Java

yes

proprietary syntax

Triggers

yes

by integration with AWS Lambda

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

Implicit feature of the cloud service

Sharding

none

yes

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Implicit feature of the cloud service

yes

none

yes

Multi-source replication
Source-replica replication

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

none

Immediate Consistency

Eventual Consistency across shards
Immediate Consistency within a shard

Foreign keys

Referential integrity

yes

not for MyISAM storage engine

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

yes

ACID at shard level

Concurrency

Support for concurrent manipulation of data

yes

table locks or row locks depending on storage engine

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

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

granular access controls, API key management, content filters

Users with fine-grained authorization concept

no user groups or 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.