DBMS > Amazon DynamoDB vs. Google Cloud Datastore vs. Kinetica vs. Microsoft Azure SQL Database vs. searchxml

System Properties Comparison Amazon DynamoDB vs. Google Cloud Datastore vs. Kinetica vs. Microsoft Azure SQL Database vs. searchxml

Editorial information provided by DB-Engines

Name

Description

Hosted, scalable database service by Amazon with the data stored in Amazons cloud

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

Fully vectorized database across both GPUs and CPUs

Database as a Service offering with high compatibility to Microsoft SQL Server

DBMS for structured and unstructured content wrapped with an application server

Primary database model

Document store
Key-value store

Document store

Relational DBMS

Native XML DBMS
Search engine

Secondary database models

Spatial DBMS
Time Series DBMS

Document store
Graph DBMS
Spatial DBMS

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

Score	77.57
Rank	#16	Overall
	#2	Document stores
	#2	Key-value stores

Score	4.49
Rank	#79	Overall
	#12	Document stores

Score	0.69
Rank	#234	Overall
	#107	Relational DBMS

Score	78.40
Rank	#15	Overall
	#10	Relational DBMS

Score	0.01
Rank	#386	Overall
	#7	Native XML DBMS
	#24	Search engines

Website

aws.amazon.com/dynamodb

cloud.google.com/datastore

www.kinetica.com

azure.microsoft.com/en-us/products/azure-sql/database

www.searchxml.net/category/products

Technical documentation

docs.aws.amazon.com/dynamodb

cloud.google.com/datastore/docs

docs.kinetica.com

docs.microsoft.com/en-us/azure/azure-sql

www.searchxml.net/support/handouts

Developer

Amazon

Google

Kinetica

Microsoft

informationpartners gmbh

Initial release

2012

2008

2012

2010

2015

Current release

7.1, August 2021

V12

1.0

License

Commercial or Open Source

commercial

free tier for a limited amount of database operations

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

C, C++

C++

Server operating systems

hosted

Linux

hosted

Windows

Data scheme

schema-free

yes

schema-free

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

SQL-like query language (GQL)

SQL-like DML and DDL statements

yes

APIs and other access methods

RESTful HTTP API

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

JDBC
ODBC
RESTful HTTP API

ADO.NET
JDBC
ODBC

RESTful HTTP API
WebDAV
XQuery
XSLT

Supported programming languages

.Net
ColdFusion
Erlang
Groovy
Java
JavaScript
Perl
PHP
Python
Ruby

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

C++
Java
JavaScript (Node.js)
Python

.Net
C#
Java
JavaScript (Node.js)
PHP
Python
Ruby

C++

most other programming languages supported via APIs

Server-side scripts

Stored procedures

using Google App Engine

user defined functions

Transact SQL

yes

on the application server

Triggers

yes

by integration with AWS Lambda

Callbacks using the Google Apps Engine

yes

triggers when inserted values for one or more columns fall within a specified range

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Multi-source replication using Paxos

Source-replica replication

yes, with always 3 replicas available

yes

sychronisation to multiple collections

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

Eventual Consistency
Immediate Consistency

can be specified for read operations

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 or Eventual Consistency depending on configuration

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

ACID across one or more tables within a single AWS account and region

ACID

Serializable Isolation within Transactions, Read Committed outside of Transactions

ACID

multiple readers, single writer

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

GPU vRAM or System RAM

User concepts

Access control

Access rights for users and roles can be defined via the AWS Identity and Access Management (IAM)

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

Access rights for users and roles on table level

fine grained access rights according to SQL-standard

Domain, group and role-based access control at the document level and for application services

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.