DBMS > Alibaba Cloud MaxCompute vs. BoltDB vs. Google Cloud Datastore vs. Microsoft Azure Cosmos DB vs. Netezza

System Properties Comparison Alibaba Cloud MaxCompute vs. BoltDB vs. Google Cloud Datastore vs. Microsoft Azure Cosmos DB vs. Netezza

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

An embedded key-value store for Go.

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

Globally distributed, horizontally scalable, multi-model database service

Data warehouse and analytics appliance part of IBM PureSystems

Primary database model

Relational DBMS

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

Key-value store

Document store

Document store
Graph DBMS
Key-value store
Wide column store

Relational DBMS

Secondary database models

Spatial DBMS

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

Score	0.84
Rank	#209	Overall
	#98	Relational DBMS

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

Score	4.36
Rank	#72	Overall
	#12	Document stores

Score	27.71
Rank	#27	Overall
	#4	Document stores
	#2	Graph DBMS
	#3	Key-value stores
	#3	Wide column stores

Score	8.59
Rank	#45	Overall
	#29	Relational DBMS

Website

www.alibabacloud.com/product/maxcompute

github.com/boltdb/bolt

cloud.google.com/datastore

azure.microsoft.com/services/cosmos-db

www.ibm.com/products/netezza

Technical documentation

www.alibabacloud.com/help/en/maxcompute

cloud.google.com/datastore/docs

learn.microsoft.com/azure/cosmos-db

Developer

Alibaba

Google

Microsoft

IBM

Initial release

2016

2013

2008

2014

2000

License

Commercial or Open Source

commercial

Open Source

MIT License

commercial

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

Linux

included in appliance

Data scheme

yes

schema-free

yes

Typing

predefined data types such as float or date

yes

yes, details here

yes

JSON types

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

All properties auto-indexed by default

yes

SQL

Support of SQL

SQL-like query language

SQL-like query language (GQL)

SQL-like query language

yes

APIs and other access methods

Fluentd
Flume
MaxCompute Console

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

DocumentDB API
Graph API (Gremlin)
MongoDB API
RESTful HTTP API
Table API

JDBC
ODBC
OLE DB

Supported programming languages

Java

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

.Net
C#
Java
JavaScript
JavaScript (Node.js)
MongoDB client drivers written for various programming languages
Python

C
C++
Fortran
Java
Lua
Perl
Python
R

Server-side scripts

Stored procedures

user defined functions

in Java

using Google App Engine

JavaScript

yes

Triggers

Callbacks using the Google Apps Engine

JavaScript

Partitioning methods

Methods for storing different data on different nodes

Sharding

Implicit feature of the cloud service

none

Sharding

Implicit feature of the cloud service

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Implicit feature of the cloud service

none

Multi-source replication using Paxos

yes

Implicit feature of the cloud service

Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

using Google Cloud Dataflow

with Hadoop integration

Integration with Hadoop/HDInsight on Azure*

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

none

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.

Bounded Staleness
Consistent Prefix
Eventual Consistency
Immediate Consistency

Consistency level configurable on request level
Session Consistency

Foreign keys

Referential integrity

yes

via ReferenceProperties or Ancestor paths

Transaction concepts

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

yes

ACID

Serializable Isolation within Transactions, Read Committed outside of Transactions

Multi-item ACID transactions with snapshot isolation within a partition

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.

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)

Access rights can be defined down to the item level

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.