DBMS > Alibaba Cloud AnalyticDB for MySQL vs. Apache Phoenix vs. Google Cloud Datastore vs. Microsoft SQL Server vs. Realm

System Properties Comparison Alibaba Cloud AnalyticDB for MySQL vs. Apache Phoenix vs. Google Cloud Datastore vs. Microsoft SQL Server vs. Realm

Editorial information provided by DB-Engines

Name

Description

A real-time data warehousing service that can process petabytes of data with high concurrency and low latency. It is fully compatible with the MySQL protocol.

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

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

Microsofts flagship relational DBMS

A DBMS built for use on mobile devices that’s a fast, easy to use alternative to SQLite and Core Data

Primary database model

Secondary database models

Document store

Document store
Graph DBMS
Spatial DBMS

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

Score	0.85
Rank	#207	Overall
	#96	Relational DBMS

Score	1.97
Rank	#126	Overall
	#59	Relational DBMS

Score	4.47
Rank	#76	Overall
	#12	Document stores

Score	824.29
Rank	#3	Overall
	#3	Relational DBMS

Score	7.60
Rank	#52	Overall
	#9	Document stores

Website

www.alibabacloud.com/product/analyticdb-for-mysql

phoenix.apache.org

cloud.google.com/datastore

www.microsoft.com/en-us/sql-server

realm.io

Technical documentation

www.alibabacloud.com/help/doc-detail/93776.htm

phoenix.apache.org

cloud.google.com/datastore/docs

learn.microsoft.com/en-US/sql/sql-server

realm.io/docs

Developer

Alibaba

Apache Software Foundation

Google

Microsoft

Realm, acquired by MongoDB in May 2019

Initial release

2014

2008

1989

2014

Current release

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

SQL Server 2022, November 2022

License

Commercial or Open Source

commercial

Open Source

Apache Version 2.0

commercial

restricted free version is available

Open Source

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

C++

Server operating systems

hosted

Linux
Unix
Windows

hosted

Linux
Windows

Android
Backend: server-less
iOS
Windows

Data scheme

yes

late-bound, schema-on-read capabilities

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.

yes

Secondary indexes

yes

SQL

Support of SQL

yes

SQL-like query language (GQL)

yes

APIs and other access methods

JDBC
ODBC

JDBC

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

ADO.NET
JDBC
ODBC
OLE DB
Tabular Data Stream (TDS)

Supported programming languages

C#
Java
PHP
Python

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

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

C#
C++
Delphi
Go
Java
JavaScript (Node.js)
PHP
Python
R
Ruby
Visual Basic

.Net
Java

with Android only
Objective-C
React Native
Swift

Server-side scripts

Stored procedures

yes

user defined functions

using Google App Engine

Transact SQL, .NET languages, R, Python and (with SQL Server 2019) Java

runs within the applications so server-side scripts are unnecessary

Triggers

yes

Callbacks using the Google Apps Engine

yes

Change Listeners

Partitioning methods

Methods for storing different data on different nodes

Sharding

Implicit feature of the cloud service

Sharding

tables can be distributed across several files (horizontal partitioning); sharding through federation

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Implicit feature of the cloud service

Multi-source replication
Source-replica replication

Multi-source replication using Paxos

yes, but depending on the SQL-Server Edition

none

MapReduce

Offers an API for user-defined Map/Reduce methods

Hadoop integration

yes

using Google Cloud Dataflow

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Immediate Consistency or Eventual 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.

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

In-Memory realm

User concepts

Access control

fine grained access rights according to SQL-standard

Access Control Lists (using HBase ACL) for RBAC, integration with Apache Ranger for RBAC & ABAC, multi-tenancy

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

fine grained access rights according to SQL-standard

yes

More information provided by the system vendor

Specific characteristics

A real-time data warehousing service that can process PB data with high concurrency...
» more

Competitive advantages

TPC Benchmark: The world leading result in TPC-DS benchmark . TPC-H benchmark for...
» more

Licensing and pricing models

Available regions: America US Virginia US Silicon Valley Asia China Hong Kong India...
» more

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.