DBMS > Google Cloud Datastore vs. LevelDB vs. Microsoft Azure Cosmos DB vs. searchxml vs. SWC-DB

System Properties Comparison Google Cloud Datastore vs. LevelDB vs. Microsoft Azure Cosmos DB vs. searchxml vs. SWC-DB

Editorial information provided by DB-Engines

Name

Description

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

Embeddable fast key-value storage library that provides an ordered mapping from string keys to string values

Globally distributed, horizontally scalable, multi-model database service

DBMS for structured and unstructured content wrapped with an application server

A high performance, scalable Wide Column DBMS

Primary database model

Document store

Key-value store

Document store
Graph DBMS
Key-value store
Wide column store

Native XML DBMS
Search engine

Wide column store

Secondary database models

Spatial DBMS

Time Series DBMS

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

Score	4.36
Rank	#72	Overall
	#12	Document stores

Score	2.25
Rank	#115	Overall
	#19	Key-value stores

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

Score	0.03
Rank	#390	Overall
	#7	Native XML DBMS
	#24	Search engines

Score	0.08
Rank	#364	Overall
	#13	Wide column stores

Website

cloud.google.com/datastore

github.com/google/leveldb

azure.microsoft.com/services/cosmos-db

www.searchxml.net/category/products

github.com/kashirin-alex/swc-db
www.swcdb.org

Technical documentation

cloud.google.com/datastore/docs

github.com/google/leveldb/blob/main/doc/index.md

learn.microsoft.com/azure/cosmos-db

www.searchxml.net/support/handouts

Developer

Google

Microsoft

informationpartners gmbh

Alex Kashirin

Initial release

2008

2011

2014

2015

2020

Current release

1.23, February 2021

1.0

0.5, April 2021

License

Commercial or Open Source

commercial

Open Source

BSD

commercial

Open Source

GPL V3

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

Server operating systems

hosted

Illumos
Linux
OS X
Windows

hosted

Windows

Linux

Data scheme

schema-free

Typing

predefined data types such as float or date

yes, details here

yes

JSON types

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

All properties auto-indexed by default

yes

SQL

Support of SQL

SQL-like query language (GQL)

SQL-like query language

APIs and other access methods

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

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

RESTful HTTP API
WebDAV
XQuery
XSLT

Proprietary protocol
Thrift

Supported programming languages

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

C++
Go
Java

3rd party binding
JavaScript (Node.js)

3rd party binding
Python

3rd party binding

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

C++

most other programming languages supported via APIs

C++

Server-side scripts

Stored procedures

using Google App Engine

JavaScript

yes

on the application server

Triggers

Callbacks using the Google Apps Engine

JavaScript

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

Sharding

Implicit feature of the cloud service

none

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication using Paxos

none

yes

Implicit feature of the cloud service

yes

sychronisation to multiple collections

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

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

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

multiple readers, single writer

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

with automatic compression on writes

yes

In-memory capabilities

Is there an option to define some or all structures to be held in-memory only.

User concepts

Access control

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

Access rights can be defined down to the item level

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.