DBMS > Microsoft Azure Cosmos DB vs. Microsoft Azure Table Storage vs. Realm vs. Sadas Engine vs. Transbase

System Properties Comparison Microsoft Azure Cosmos DB vs. Microsoft Azure Table Storage vs. Realm vs. Sadas Engine vs. Transbase

Editorial information provided by DB-Engines

Name

Description

Globally distributed, horizontally scalable, multi-model database service

A Wide Column Store for rapid development using massive semi-structured datasets

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

SADAS Engine is a columnar DBMS specifically designed for high performance in data warehouse environments

A resource-optimized, high-performance, universally applicable RDBMS

Primary database model

Document store
Graph DBMS
Key-value store
Wide column store

Wide column store

Document store

Relational DBMS

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	4.48
Rank	#75	Overall
	#6	Wide column stores

Score	7.60
Rank	#52	Overall
	#9	Document stores

Score	0.00
Rank	#383	Overall
	#158	Relational DBMS

Score	0.11
Rank	#341	Overall
	#150	Relational DBMS

Website

azure.microsoft.com/services/cosmos-db

azure.microsoft.com/en-us/services/storage/tables

realm.io

www.sadasengine.com

www.transaction.de/en/products/transbase.html

Technical documentation

learn.microsoft.com/azure/cosmos-db

realm.io/docs

www.sadasengine.com/en/sadas-engine-download-free-trial-and-documentation/#documentation

www.transaction.de/en/products/transbase/features.html

Developer

Microsoft

Realm, acquired by MongoDB in May 2019

SADAS s.r.l.

Transaction Software GmbH

Initial release

2014

2012

2014

2006

1987

Current release

8.0

Transbase 8.3, 2022

License

Commercial or Open Source

commercial

Open Source

commercial

free trial version available

commercial

free development license

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

Server operating systems

hosted

Android
Backend: server-less
iOS
Windows

AIX
Linux
Windows

FreeBSD
Linux
macOS
Solaris
Windows

Data scheme

schema-free

yes

Typing

predefined data types such as float or date

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.

Secondary indexes

yes

All properties auto-indexed by default

yes

SQL

Support of SQL

SQL-like query language

yes

APIs and other access methods

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

RESTful HTTP API

JDBC
ODBC
Proprietary protocol

ADO.NET
JDBC
ODBC
Proprietary native API

Supported programming languages

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

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

.Net
Java

with Android only
Objective-C
React Native
Swift

.Net
C
C#
C++
Groovy
Java
PHP
Python

C
C#
C++
Java
JavaScript
Kotlin
Objective-C
PHP
Python

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

Implicit feature of the cloud service

none

horizontal partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Implicit feature of the cloud service

yes

implicit feature of the cloud service. Replication either local, cross-facility or geo-redundant.

none

Source-replica replication

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

Foreign keys

Referential integrity

yes

Transaction concepts

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

Multi-item ACID transactions with snapshot isolation within a partition

optimistic locking

ACID

yes

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

yes

managed by 'Learn by Usage'

User concepts

Access control

Access rights can be defined down to the item level

Access rights based on private key authentication or shared access signatures

yes

Access rights for users, groups and roles according to SQL-standard

fine grained access rights according to SQL-standard

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.