DBMS > Alibaba Cloud MaxCompute vs. Apache Phoenix vs. Google BigQuery vs. TDSQL for MySQL vs. TinkerGraph

System Properties Comparison Alibaba Cloud MaxCompute vs. Apache Phoenix vs. Google BigQuery vs. TDSQL for MySQL vs. TinkerGraph

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

A scale-out RDBMS with evolutionary schema built on Apache HBase

Large scale data warehouse service with append-only tables

A high-performance distributed database management system with features such as automatic sharding, intelligent operation and maintenance, elastic scalability without downtime, and enterprise-grade security. It is highly compatible with MySQL.

A lightweight, in-memory graph engine that serves as a reference implementation of the TinkerPop3 API

Primary database model

Relational DBMS

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

Relational DBMS

Graph DBMS

Secondary database models

Document store
Spatial DBMS

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

Score	0.77
Rank	#214	Overall
	#98	Relational DBMS

Score	1.97
Rank	#126	Overall
	#59	Relational DBMS

Score	60.38
Rank	#19	Overall
	#13	Relational DBMS

Score	0.85
Rank	#205	Overall
	#95	Relational DBMS

Score	0.08
Rank	#348	Overall
	#35	Graph DBMS

Website

www.alibabacloud.com/product/maxcompute

phoenix.apache.org

cloud.google.com/bigquery

www.tencentcloud.com/products/dcdb

tinkerpop.apache.org/docs/current/reference/#tinkergraph-gremlin

Technical documentation

www.alibabacloud.com/help/en/maxcompute

phoenix.apache.org

cloud.google.com/bigquery/docs

www.tencentcloud.com/document/product/1042

Developer

Alibaba

Apache Software Foundation

Google

Tencent

Initial release

2016

2014

2010

2013

2009

Current release

5.0-HBase2, July 2018 and 4.15-HBase1, December 2019

License

Commercial or Open Source

commercial

Open Source

Apache Version 2.0

commercial

Open Source

Apache 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

Server operating systems

hosted

Linux
Unix
Windows

hosted

Data scheme

yes

late-bound, schema-on-read capabilities

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.

Secondary indexes

yes

SQL

Support of SQL

SQL-like query language

yes

APIs and other access methods

Fluentd
Flume
MaxCompute Console

JDBC

RESTful HTTP/JSON API

JDBC
ODBC

TinkerPop 3

Supported programming languages

Java

C
C#
C++
Go
Groovy
Java
PHP
Python
Scala

.Net
Java
JavaScript
Objective-C
PHP
Python
Ruby

C
C#
C++
Java
PHP
Python
Ruby

Groovy
Java

Server-side scripts

Stored procedures

user defined functions

in Java

user defined functions

in JavaScript

yes

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

Implicit feature of the cloud service

Sharding

none

Automatic sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Implicit feature of the cloud service

Multi-source replication
Source-replica replication

none

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Hadoop integration

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Immediate Consistency or Eventual Consistency

Immediate Consistency

none

Foreign keys

Referential integrity

yes

Relationships in graphs

Transaction concepts

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

ACID

Since BigQuery is designed for querying data

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

optional

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 Control Lists (using HBase ACL) for RBAC, integration with Apache Ranger for RBAC & ABAC, multi-tenancy

Access privileges (owner, writer, reader) on dataset, table or view level

Google Cloud Identity & Access Management (IAM)

Users with fine-grained authorization concept

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.