DBMS > Alibaba Cloud MaxCompute vs. Google BigQuery vs. KairosDB vs. Postgres-XL vs. Yanza

System Properties Comparison Alibaba Cloud MaxCompute vs. Google BigQuery vs. KairosDB vs. Postgres-XL vs. Yanza

Editorial information provided by DB-Engines

Name

Yanza seems to be discontinued. Therefore it is excluded from the DB-Engines Ranking.

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 with append-only tables

Distributed Time Series DBMS based on Cassandra or H2

Based on PostgreSQL enhanced with MPP and write-scale-out cluster features

Time Series DBMS for IoT Applications

Primary database model

Relational DBMS

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

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	58.10
Rank	#19	Overall
	#13	Relational DBMS

Score	0.67
Rank	#233	Overall
	#20	Time Series DBMS

Score	0.53
Rank	#254	Overall
	#117	Relational DBMS

Website

www.alibabacloud.com/product/maxcompute

cloud.google.com/bigquery

github.com/kairosdb/kairosdb

www.postgres-xl.org

yanza.com

Technical documentation

www.alibabacloud.com/help/en/maxcompute

cloud.google.com/bigquery/docs

kairosdb.github.io

www.postgres-xl.org/documentation

Developer

Alibaba

Google

Yanza

Initial release

2016

2010

2013

2014

since 2012, originally named StormDB

2015

Current release

1.2.2, November 2018

10 R1, October 2018

License

Commercial or Open Source

commercial

Open Source

Apache 2.0

Open Source

Mozilla public license

commercial

free version available

Cloud-based only

Only available as a cloud service

yes

but mainly used as a service provided by Yanza

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
OS X
Windows

Linux
macOS

Windows

Data scheme

yes

schema-free

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

XML type, but no XML query functionality

Secondary indexes

yes

SQL

Support of SQL

SQL-like query language

yes

distributed, parallel query execution

APIs and other access methods

Fluentd
Flume
MaxCompute Console

RESTful HTTP/JSON API

Graphite protocol
HTTP REST
Telnet API

ADO.NET
JDBC
native C library
ODBC
streaming API for large objects

HTTP API

Supported programming languages

Java

.Net
Java
JavaScript
Objective-C
PHP
Python
Ruby

Java
JavaScript

Node.js
PHP
Python

.Net
C
C++
Delphi
Erlang
Java
JavaScript (Node.js)
Perl
PHP
Python
Tcl

any language that supports HTTP calls

Server-side scripts

Stored procedures

user defined functions

in Java

user defined functions

in JavaScript

user defined functions

Triggers

yes

Timer and event based

Partitioning methods

Methods for storing different data on different nodes

Sharding

Implicit feature of the cloud service

none

Sharding

based on Cassandra

horizontal partitioning

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Implicit feature of the cloud service

selectable replication factor

based on Cassandra

none

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

based on Cassandra
Immediate Consistency

based on Cassandra

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

Since BigQuery is designed for querying data

ACID

MVCC

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.

User concepts

Access control

Access rights for users and roles

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

Google Cloud Identity & Access Management (IAM)

simple password-based access control

fine grained access rights according to SQL-standard

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.