DBMS > Google Cloud Datastore vs. Kinetica vs. Microsoft Azure Cosmos DB vs. STSdb vs. WakandaDB

System Properties Comparison Google Cloud Datastore vs. Kinetica vs. Microsoft Azure Cosmos DB vs. STSdb vs. WakandaDB

Editorial information provided by DB-Engines

Name

Description

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

Fully vectorized database across both GPUs and CPUs

Globally distributed, horizontally scalable, multi-model database service

Key-Value Store with special method for indexing

optimized for high performance using a special indexing method

WakandaDB is embedded in a server that provides a REST API and a server-side javascript engine to access data

Primary database model

Document store

Relational DBMS

Document store
Graph DBMS
Key-value store
Wide column store

Key-value store

Object oriented DBMS

Secondary database models

Spatial DBMS
Time Series DBMS

Spatial DBMS

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

Score	4.36
Rank	#72	Overall
	#12	Document stores

Score	0.66
Rank	#234	Overall
	#107	Relational DBMS

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

Score	0.10
Rank	#357	Overall
	#51	Key-value stores

Score	0.10
Rank	#356	Overall
	#16	Object oriented DBMS

Website

cloud.google.com/datastore

www.kinetica.com

azure.microsoft.com/services/cosmos-db

github.com/STSSoft/STSdb4

wakanda.github.io

Technical documentation

cloud.google.com/datastore/docs

docs.kinetica.com

learn.microsoft.com/azure/cosmos-db

wakanda.github.io/doc

Developer

Google

Kinetica

Microsoft

STS Soft SC

Wakanda SAS

Initial release

2008

2012

2014

2011

2012

Current release

7.1, August 2021

4.0.8, September 2015

2.7.0 (April 29, 2019), April 2019

License

Commercial or Open Source

commercial

Open Source

GPLv2, commercial license available

Open Source

AGPLv3, extended commercial license available

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++, JavaScript

Server operating systems

hosted

Linux

hosted

Windows

Linux
OS X
Windows

Data scheme

schema-free

yes

schema-free

yes

Typing

predefined data types such as float or date

yes, details here

yes

JSON types

yes

primitive types and user defined types (classes)

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

SQL

Support of SQL

SQL-like query language (GQL)

SQL-like DML and DDL statements

SQL-like query language

APIs and other access methods

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

JDBC
ODBC
RESTful HTTP API

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

.NET Client API

RESTful HTTP API

Supported programming languages

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

C++
Java
JavaScript (Node.js)
Python

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

C#
Java

JavaScript

Server-side scripts

Stored procedures

using Google App Engine

user defined functions

JavaScript

yes

Triggers

Callbacks using the Google Apps Engine

yes

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

JavaScript

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

Implicit feature of the cloud service

none

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication using Paxos

Source-replica replication

yes

Implicit feature of the cloud service

none

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

using Google Cloud Dataflow

with Hadoop integration

Integration with Hadoop/HDInsight on Azure*

Consistency concepts

Methods to ensure consistency in a distributed system

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

Bounded Staleness
Consistent Prefix
Eventual Consistency
Immediate Consistency

Consistency level configurable on request level
Session Consistency

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

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.

yes

GPU vRAM or System RAM

User concepts

Access control

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

Access rights can be defined down to the item level

yes

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.