DBMS > Atos Standard Common Repository vs. Google Cloud Datastore vs. Microsoft Azure Cosmos DB vs. SiteWhere vs. SWC-DB

System Properties Comparison Atos Standard Common Repository vs. Google Cloud Datastore vs. Microsoft Azure Cosmos DB vs. SiteWhere vs. SWC-DB

Editorial information provided by DB-Engines

Name

This system has been discontinued and will be removed from the DB-Engines ranking.

Description

Highly scalable database system, designed for managing session and subscriber data in modern mobile communication networks

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

Globally distributed, horizontally scalable, multi-model database service

M2M integration platform for persisting/querying time series data

A high performance, scalable Wide Column DBMS

Primary database model

Document store
Key-value store

Document store

Document store
Graph DBMS
Key-value store
Wide column store

Time Series DBMS

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	27.71
Rank	#27	Overall
	#4	Document stores
	#2	Graph DBMS
	#3	Key-value stores
	#3	Wide column stores

Score	0.06
Rank	#383	Overall
	#43	Time Series DBMS

Score	0.08
Rank	#364	Overall
	#13	Wide column stores

Website

atos.net/en/convergence-creators/portfolio/standard-common-repository

cloud.google.com/datastore

azure.microsoft.com/services/cosmos-db

github.com/sitewhere/sitewhere

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

Technical documentation

cloud.google.com/datastore/docs

learn.microsoft.com/azure/cosmos-db

sitewhere1.sitewhere.io/index.html

Developer

Atos Convergence Creators

Google

Microsoft

SiteWhere

Alex Kashirin

Initial release

2016

2008

2014

2010

2020

Current release

1703

0.5, April 2021

License

Commercial or Open Source

commercial

Open Source

Common Public Attribution License Version 1.0

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

Java

C++

Server operating systems

Linux

hosted

Linux
OS X
Windows

Linux

Data scheme

Schema and schema-less with LDAP views

schema-free

predefined scheme

schema-free

Typing

predefined data types such as float or date

optional

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

SQL

Support of SQL

SQL-like query language (GQL)

SQL-like query language

APIs and other access methods

LDAP

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

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

HTTP REST

Proprietary protocol
Thrift

Supported programming languages

All languages with LDAP bindings

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

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

C++

Server-side scripts

Stored procedures

using Google App Engine

JavaScript

Triggers

yes

Callbacks using the Google Apps Engine

JavaScript

Partitioning methods

Methods for storing different data on different nodes

Sharding

cell division

Sharding

Implicit feature of the cloud service

Sharding

based on HBase

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Multi-source replication using Paxos

yes

Implicit feature of the cloud service

selectable replication factor

based on HBase

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 configuration

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.

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

Atomic execution of specific operations

ACID

Serializable Isolation within Transactions, Read Committed outside of Transactions

Multi-item ACID transactions with snapshot isolation within a partition

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

User concepts

Access control

LDAP bind authentication

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

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.