DBMS > Alibaba Cloud MaxCompute vs. GBase vs. Google Cloud Datastore vs. SQLite

System Properties Comparison Alibaba Cloud MaxCompute vs. GBase vs. Google Cloud Datastore vs. SQLite

Please select another system to include it in the comparison.

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

Widely used RDBMS in China, including analytical, transactional, distributed transactional, and cloud-native data warehousing.

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

Widely used embeddable, in-process RDBMS

Primary database model

Relational DBMS

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

Relational DBMS

Document store

Relational DBMS

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

Score	0.85
Rank	#203	Overall
	#96	Relational DBMS

Score	1.11
Rank	#173	Overall
	#78	Relational DBMS

Score	4.13
Rank	#71	Overall
	#12	Document stores

Score	103.35
Rank	#10	Overall
	#7	Relational DBMS

Website

www.alibabacloud.com/product/maxcompute

www.gbase.cn

cloud.google.com/datastore

www.sqlite.org

Technical documentation

www.alibabacloud.com/help/en/maxcompute

cloud.google.com/datastore/docs

www.sqlite.org/docs.html

Developer

Alibaba

General Data Technology Co., Ltd.

Google

Dwayne Richard Hipp

Initial release

2016

2004

2008

2000

Current release

GBase 8a, GBase 8s, GBase 8c

3.46.1 (13 August 2024), August 2024

License

Commercial or Open Source

commercial

Open Source

Public Domain

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

C, Java, Python

Server operating systems

hosted

Linux

hosted

server-less

Data scheme

yes

schema-free

yes

dynamic column types

Typing

predefined data types such as float or date

yes

yes, details here

yes

not rigid because of 'dynamic typing' concept.

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

Secondary indexes

yes

SQL

Support of SQL

SQL-like query language

Standard with numerous extensions

SQL-like query language (GQL)

yes

SQL-92 is not fully supported

APIs and other access methods

Fluentd
Flume
MaxCompute Console

ADO.NET
C API
JDBC
ODBC

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

ADO.NET

inofficial driver
JDBC

inofficial driver
ODBC

inofficial driver

Supported programming languages

Java

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

Actionscript
Ada
Basic
C
C#
C++
D
Delphi
Forth
Fortran
Haskell
Java
JavaScript
Lisp
Lua
MatLab
Objective-C
OCaml
Perl
PHP
PL/SQL
Python
R
Ruby
Scala
Scheme
Smalltalk
Tcl

Server-side scripts

Stored procedures

user defined functions

in Java

user defined functions

using Google App Engine

Triggers

yes

Callbacks using the Google Apps Engine

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

Implicit feature of the cloud service

horizontal partitioning (by range, list and hash) and vertical partitioning

Sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Implicit feature of the cloud service

yes

Multi-source replication using Paxos

none

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

using Google Cloud Dataflow

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.

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

via file-system locks

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

yes

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

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.