DBMS > Microsoft Azure Cosmos DB vs. OpenTSDB vs. Realm vs. STSdb vs. WakandaDB

System Properties Comparison Microsoft Azure Cosmos DB vs. OpenTSDB vs. Realm vs. STSdb vs. WakandaDB

Editorial information provided by DB-Engines

Name

Description

Globally distributed, horizontally scalable, multi-model database service

Scalable Time Series DBMS based on HBase

A DBMS built for use on mobile devices that’s a fast, easy to use alternative to SQLite and Core Data

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
Graph DBMS
Key-value store
Wide column store

Secondary database models

Spatial DBMS

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

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

Score	1.68
Rank	#146	Overall
	#12	Time Series DBMS

Score	7.60
Rank	#52	Overall
	#9	Document stores

Score	0.04
Rank	#360	Overall
	#52	Key-value stores

Score	0.03
Rank	#364	Overall
	#17	Object oriented DBMS

Website

azure.microsoft.com/services/cosmos-db

opentsdb.net

realm.io

github.com/STSSoft/STSdb4

wakanda.github.io

Technical documentation

learn.microsoft.com/azure/cosmos-db

opentsdb.net/docs/build/html/index.html

realm.io/docs

wakanda.github.io/doc

Developer

Microsoft

currently maintained by Yahoo and other contributors

Realm, acquired by MongoDB in May 2019

STS Soft SC

Wakanda SAS

Initial release

2014

2011

2014

2011

2012

Current release

4.0.8, September 2015

2.7.0 (April 29, 2019), April 2019

License

Commercial or Open Source

commercial

Open Source

LGPL

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

Java

C++, JavaScript

Server operating systems

hosted

Linux
Windows

Android
Backend: server-less
iOS
Windows

Windows

Linux
OS X
Windows

Data scheme

schema-free

yes

Typing

predefined data types such as float or date

yes

JSON types

numeric data for metrics, strings for tags

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

yes

SQL

Support of SQL

SQL-like query language

APIs and other access methods

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

HTTP API
Telnet API

.NET Client API

RESTful HTTP API

Supported programming languages

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

Erlang
Go
Java
Python
R
Ruby

.Net
Java

with Android only
Objective-C
React Native
Swift

C#
Java

JavaScript

Server-side scripts

Stored procedures

JavaScript

runs within the applications so server-side scripts are unnecessary

yes

Triggers

JavaScript

yes

Change Listeners

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

Implicit feature of the cloud service

Sharding

based on HBase

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Implicit feature of the cloud service

selectable replication factor

based on HBase

none

MapReduce

Offers an API for user-defined Map/Reduce methods

with Hadoop integration

Integration with Hadoop/HDInsight on Azure*

Consistency concepts

Methods to ensure consistency in a distributed system

Bounded Staleness
Consistent Prefix
Eventual Consistency
Immediate Consistency

Consistency level configurable on request level
Session Consistency

Immediate Consistency

based on HBase

Immediate Consistency

Foreign keys

Referential integrity

Transaction concepts

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

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

In-Memory realm

User concepts

Access control

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.