DBMS > Alibaba Cloud MaxCompute vs. Google Cloud Datastore vs. KairosDB vs. SAP HANA vs. YTsaurus

System Properties Comparison Alibaba Cloud MaxCompute vs. Google Cloud Datastore vs. KairosDB vs. SAP HANA vs. YTsaurus

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

Automatically scaling NoSQL Database as a Service (DBaaS) on the Google Cloud Platform

Distributed Time Series DBMS based on Cassandra or H2

In-memory, column based data store. Available as appliance or cloud service

YTsaurus is an open source platform for distributed storage and processing.

Primary database model

Relational DBMS

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

Document store

Time Series DBMS

Relational DBMS

Document store
Key-value store

Secondary database models

Document store
Graph DBMS

with SAP Hana, Enterprise Edition
Spatial DBMS

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

Score	0.84
Rank	#209	Overall
	#98	Relational DBMS

Score	4.36
Rank	#72	Overall
	#12	Document stores

Score	0.67
Rank	#233	Overall
	#20	Time Series DBMS

Score	44.27
Rank	#23	Overall
	#16	Relational DBMS

Score	0.21
Rank	#324	Overall
	#45	Document stores
	#48	Key-value stores

Website

www.alibabacloud.com/product/maxcompute

cloud.google.com/datastore

github.com/kairosdb/kairosdb

www.sap.com/products/hana.html

ytsaurus.tech

Technical documentation

www.alibabacloud.com/help/en/maxcompute

cloud.google.com/datastore/docs

kairosdb.github.io

help.sap.com/hana

ytsaurus.tech/docs/en

Developer

Alibaba

Google

SAP

Yandex

Initial release

2016

2008

2013

2010

2023

Current release

1.2.2, November 2018

2.0 SPS07 (April 4, 2023), April 2023

License

Commercial or Open Source

commercial

Open Source

Apache 2.0

commercial

Open Source

Apache License, Version 2.0

Cloud-based only

Only available as a cloud service

yes

also available as a cloud based service

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

Appliance or cloud-service

Ubuntu

Data scheme

yes

schema-free

yes

Typing

predefined data types such as float or date

yes

yes, details here

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

SQL-like query language (GQL)

yes

YQL, an SQL-based language, is supported

APIs and other access methods

Fluentd
Flume
MaxCompute Console

gRPC (using protocol buffers) API
RESTful HTTP/JSON API

Graphite protocol
HTTP REST
Telnet API

JDBC
ODBC

Supported programming languages

Java

.Net
Go
Java
JavaScript (Node.js)
PHP
Python
Ruby

Java
JavaScript

Node.js
PHP
Python

C++
Go
Java
JavaScript
Python

Server-side scripts

Stored procedures

user defined functions

in Java

using Google App Engine

SQLScript, R

Triggers

Callbacks using the Google Apps Engine

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

Implicit feature of the cloud service

Sharding

based on Cassandra

yes

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Implicit feature of the cloud service

Multi-source replication using Paxos

selectable replication factor

based on Cassandra

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

using Google Cloud Dataflow

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Immediate Consistency or Eventual Consistency depending on type of query and configuration

Strong Consistency is default for entity lookups and queries within an Entity Group (but can instead be made eventually consistent). Other queries are always eventual consistent.

Eventual Consistency

based on Cassandra
Immediate Consistency

based on Cassandra

Immediate Consistency

Foreign keys

Referential integrity

yes

via ReferenceProperties or Ancestor paths

yes

Transaction concepts

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

ACID

Serializable Isolation within Transactions, Read Committed outside of Transactions

ACID

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

User concepts

Access control

Access rights for users and roles

Access rights for users, groups and roles based on Google Cloud Identity and Access Management (IAM)

simple password-based access control

yes

Access Control Lists

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.