DBMS > Amazon DocumentDB vs. Google Cloud Datastore vs. NSDb vs. SAP HANA vs. TDSQL for MySQL

System Properties Comparison Amazon DocumentDB vs. Google Cloud Datastore vs. NSDb vs. SAP HANA vs. TDSQL for MySQL

Editorial information provided by DB-Engines

Name

Description

Fast, scalable, highly available, and fully managed MongoDB-compatible database service

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

Scalable, High-performance Time Series DBMS designed for Real-time Analytics on top of Kubernetes

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

A high-performance distributed database management system with features such as automatic sharding, intelligent operation and maintenance, elastic scalability without downtime, and enterprise-grade security. It is highly compatible with MySQL.

Primary database model

Document store

Time Series DBMS

Relational DBMS

Secondary database models

Document store
Graph DBMS

with SAP Hana, Enterprise Edition
Spatial DBMS

Document store
Spatial DBMS

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

Score	1.91
Rank	#131	Overall
	#24	Document stores

Score	4.36
Rank	#72	Overall
	#12	Document stores

Score	0.08
Rank	#369	Overall
	#40	Time Series DBMS

Score	44.27
Rank	#23	Overall
	#16	Relational DBMS

Score	0.85
Rank	#207	Overall
	#97	Relational DBMS

Website

aws.amazon.com/documentdb

cloud.google.com/datastore

nsdb.io

www.sap.com/products/hana.html

www.tencentcloud.com/products/dcdb

Technical documentation

aws.amazon.com/documentdb/resources

cloud.google.com/datastore/docs

nsdb.io/Architecture

help.sap.com/hana

www.tencentcloud.com/document/product/1042

Developer

Google

SAP

Tencent

Initial release

2019

2008

2017

2010

2013

Current release

2.0 SPS07 (April 4, 2023), April 2023

License

Commercial or Open Source

commercial

Open Source

Apache Version 2.0

commercial

Cloud-based only

Only available as a cloud service

yes

also available as a cloud based service

yes

DBaaS offerings (sponsored links)

Database as a Service

Providers of DBaaS offerings, please contact us to be listed.

Implementation language

Java, Scala

Server operating systems

hosted

Linux
macOS

Appliance or cloud-service

hosted

Data scheme

schema-free

yes

Typing

predefined data types such as float or date

yes

yes, details here

yes: int, bigint, decimal, string

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 fields are automatically indexed

yes

SQL

Support of SQL

SQL-like query language (GQL)

SQL-like query language

yes

APIs and other access methods

proprietary protocol using JSON (MongoDB compatible)

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

gRPC
HTTP REST
WebSocket

JDBC
ODBC

Supported programming languages

Go
Java
JavaScript (Node.js)
PHP
Python

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

Java
Scala

C
C#
C++
Java
PHP
Python
Ruby

Server-side scripts

Stored procedures

using Google App Engine

SQLScript, R

yes

Triggers

Callbacks using the Google Apps Engine

yes

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

yes

Automatic sharding

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-availability zones for high availability, asynchronous replication for up to 15 read replicas

Multi-source replication using Paxos

yes

Multi-source replication
Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

may be implemented via Amazon Elastic MapReduce (Amazon EMR)

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.

Eventual Consistency

Immediate Consistency

Foreign keys

Referential integrity

typically not used, however similar functionality with DBRef possible

yes

via ReferenceProperties or Ancestor paths

yes

Transaction concepts

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

Atomic single-document operations

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

Using Apache Lucene

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)

yes

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.