DBMS > HBase vs. Microsoft Azure Cosmos DB vs. Realm vs. TerarkDB

System Properties Comparison HBase vs. Microsoft Azure Cosmos DB vs. Realm vs. TerarkDB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Wide-column store based on Apache Hadoop and on concepts of BigTable

Globally distributed, horizontally scalable, multi-model database service

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

A key-value store forked from RocksDB with advanced compression algorithms. It can be used standalone or as a storage engine for MySQL and MongoDB

Primary database model

Wide column store

Document store
Graph DBMS
Key-value store
Wide column store

Document store

Key-value store

Secondary database models

Spatial DBMS

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

Score	27.97
Rank	#26	Overall
	#2	Wide column stores

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

Score	7.41
Rank	#52	Overall
	#8	Document stores

Score	0.08
Rank	#367	Overall
	#56	Key-value stores

Website

hbase.apache.org

azure.microsoft.com/services/cosmos-db

realm.io

github.com/bytedance/terarkdb

Technical documentation

hbase.apache.org/book.html

learn.microsoft.com/azure/cosmos-db

realm.io/docs

bytedance.larkoffice.com/docs/doccnZmYFqHBm06BbvYgjsHHcKc

Developer

Apache Software Foundation

Apache top-level project, originally developed by Powerset

Microsoft

Realm, acquired by MongoDB in May 2019

ByteDance, originally Terark

Initial release

2008

2014

2016

Current release

2.3.4, January 2021

License

Commercial or Open Source

Open Source

Apache version 2

commercial

Open Source

commercial

restricted open source version 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++

Server operating systems

Linux
Unix
Windows

using Cygwin

hosted

Android
Backend: server-less
iOS
Windows

Data scheme

schema-free, schema definition possible

schema-free

yes

schema-free

Typing

predefined data types such as float or date

options to bring your own types, AVRO

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

APIs and other access methods

Java API
RESTful HTTP API
Thrift

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

C++ API
Java API

Supported programming languages

C
C#
C++
Groovy
Java
PHP
Python
Scala

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

.Net
Java

with Android only
Objective-C
React Native
Swift

C++
Java

Server-side scripts

Stored procedures

yes

Coprocessors in Java

JavaScript

runs within the applications so server-side scripts are unnecessary

Triggers

yes

JavaScript

yes

Change Listeners

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
Source-replica replication

yes

Implicit feature of the cloud service

none

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

with Hadoop integration

Integration with Hadoop/HDInsight on Azure*

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency or Eventual Consistency

Bounded Staleness
Consistent Prefix
Eventual Consistency
Immediate Consistency

Consistency level configurable on request level
Session Consistency

Immediate Consistency

Foreign keys

Referential integrity

Transaction concepts

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

Single row ACID (across millions of columns)

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

yes

User concepts

Access control

Access Control Lists (ACL) for RBAC, integration with Apache Ranger for RBAC & ABAC

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.