DBMS > JanusGraph vs. Microsoft Azure Cosmos DB vs. Realm vs. RRDtool

System Properties Comparison JanusGraph vs. Microsoft Azure Cosmos DB vs. Realm vs. RRDtool

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

A Graph DBMS optimized for distributed clusters

It was forked from the latest code base of Titan in January 2017

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

Industry standard data logging and graphing tool for time series data. RRD is an acronym for round-robin database.

The data is stored in a circular buffer, thus the system storage footprint remains constant over time.

Primary database model

Graph DBMS

Document store
Graph DBMS
Key-value store
Wide column store

Document store

Time Series DBMS

Secondary database models

Spatial DBMS

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

Score	2.02
Rank	#125	Overall
	#12	Graph DBMS

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	1.90
Rank	#132	Overall
	#11	Time Series DBMS

Website

janusgraph.org

azure.microsoft.com/services/cosmos-db

realm.io

oss.oetiker.ch/rrdtool

Technical documentation

docs.janusgraph.org

learn.microsoft.com/azure/cosmos-db

realm.io/docs

oss.oetiker.ch/rrdtool/doc

Developer

Linux Foundation; originally developed as Titan by Aurelius

Microsoft

Realm, acquired by MongoDB in May 2019

Tobias Oetiker

Initial release

2017

2014

1999

Current release

0.6.3, February 2023

1.8.0, 2022

License

Commercial or Open Source

Open Source

Apache 2.0

commercial

Open Source

GPL V2 and FLOSS

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

Implementations in Java (e.g. RRD4J) and C# available

Server operating systems

Linux
OS X
Unix
Windows

hosted

Android
Backend: server-less
iOS
Windows

HP-UX
Linux

Data scheme

yes

schema-free

yes

Typing

predefined data types such as float or date

yes

JSON types

yes

Numeric data only

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.

Exporting into and restoring from XML files possible

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
TinkerPop Blueprints
TinkerPop Frames
TinkerPop Gremlin
TinkerPop Rexster

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

in-process shared library
Pipes

Supported programming languages

Clojure
Java
Python

.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

with librrd library
C#

with a different implementation of RRDTool
Java

with a different implementation of RRDTool
JavaScript (Node.js)

with a different implementation of RRDTool
Lua
Perl
PHP

with a wrapper library
Python
Ruby

Server-side scripts

Stored procedures

yes

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

yes

depending on the used storage backend (e.g. Cassandra, HBase, BerkeleyDB)

Sharding

Implicit feature of the cloud service

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Implicit feature of the cloud service

none

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

via Faunus, a graph analytics engine

with Hadoop integration

Integration with Hadoop/HDInsight on Azure*

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency
Immediate Consistency

Bounded Staleness
Consistent Prefix
Eventual Consistency
Immediate Consistency

Consistency level configurable on request level
Session Consistency

Immediate Consistency

none

Foreign keys

Referential integrity

yes

Relationships in graphs

Transaction concepts

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

ACID

Multi-item ACID transactions with snapshot isolation within a partition

ACID

Concurrency

Support for concurrent manipulation of data

yes

by using the rrdcached daemon

Durability

Support for making data persistent

yes

Supports various storage backends: Cassandra, HBase, Berkeley DB, Akiban, Hazelcast

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

User authentification and security via Rexster Graph Server

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.