DBMS > Dgraph vs. HarperDB vs. JanusGraph vs. Microsoft SQL Server vs. RRDtool

System Properties Comparison Dgraph vs. HarperDB vs. JanusGraph vs. Microsoft SQL Server vs. RRDtool

Editorial information provided by DB-Engines

Name

Description

Distributed and scalable native Graph DBMS

Ultra-low latency distributed database with an intuitive REST API supporting NoSQL and SQL (including joins). Deployment of functions and databases simultaneously with a consolidated node-level architecture.

A Graph DBMS optimized for distributed clusters

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

Microsofts flagship relational DBMS

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

Secondary database models

Document store
Graph DBMS
Spatial DBMS

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

Score	1.45
Rank	#156	Overall
	#15	Graph DBMS

Score	0.55
Rank	#248	Overall
	#38	Document stores

Score	1.94
Rank	#129	Overall
	#12	Graph DBMS

Score	824.29
Rank	#3	Overall
	#3	Relational DBMS

Score	1.87
Rank	#136	Overall
	#11	Time Series DBMS

Website

dgraph.io

www.harperdb.io

janusgraph.org

www.microsoft.com/en-us/sql-server

oss.oetiker.ch/rrdtool

Technical documentation

dgraph.io/docs

docs.harperdb.io/docs

docs.janusgraph.org

learn.microsoft.com/en-US/sql/sql-server

oss.oetiker.ch/rrdtool/doc

Developer

Dgraph Labs, Inc.

HarperDB

Linux Foundation; originally developed as Titan by Aurelius

Microsoft

Tobias Oetiker

Initial release

2016

2017

1989

1999

Current release

3.1, August 2021

0.6.3, February 2023

SQL Server 2022, November 2022

1.8.0, 2022

License

Commercial or Open Source

Open Source

Apache 2.0

commercial

free community edition available

Open Source

Apache 2.0

commercial

restricted free version is available

Open Source

GPL V2 and FLOSS

Cloud-based only

Only available as a cloud service

DBaaS offerings (sponsored links)

Database as a Service

Providers of DBaaS offerings, please contact us to be listed.

Implementation language

Node.js

Java

C++

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

Server operating systems

Linux
OS X
Windows

Linux
OS X

Linux
OS X
Unix
Windows

Linux
Windows

HP-UX
Linux

Data scheme

schema-free

dynamic schema

yes

Typing

predefined data types such as float or date

yes

JSON data 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.

yes

Exporting into and restoring from XML files possible

Secondary indexes

yes

SQL

Support of SQL

SQL-like data manipulation statements

yes

APIs and other access methods

GraphQL query language
gRPC (using protocol buffers) API
HTTP API

JDBC
ODBC
React Hooks
RESTful HTTP/JSON API
WebSocket

Java API
TinkerPop Blueprints
TinkerPop Frames
TinkerPop Gremlin
TinkerPop Rexster

ADO.NET
JDBC
ODBC
OLE DB
Tabular Data Stream (TDS)

in-process shared library
Pipes

Supported programming languages

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

.Net
C
C#
C++
ColdFusion
D
Dart
Delphi
Erlang
Go
Haskell
Java
JavaScript (Node.js)
Lisp
MatLab
Objective C
Perl
PHP
PowerShell
Prolog
Python
R
Ruby
Rust
Scala
Swift

Clojure
Java
Python

C#
C++
Delphi
Go
Java
JavaScript (Node.js)
PHP
Python
R
Ruby
Visual Basic

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

Custom Functions

since release 3.1

yes

Transact SQL, .NET languages, R, Python and (with SQL Server 2019) Java

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

yes

A table resides as a whole on one (or more) nodes in a cluster

yes

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

tables can be distributed across several files (horizontal partitioning); sharding through federation

none

Replication methods

Methods for redundantly storing data on multiple nodes

Synchronous replication via Raft

yes

the nodes on which a table resides can be defined

yes

yes, but depending on the SQL-Server Edition

none

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

via Faunus, a graph analytics engine

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency
Immediate Consistency

Immediate Consistency

none

Foreign keys

Referential integrity

yes

Relationships in graphs

yes

Transaction concepts

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

ACID

Atomic execution of specific operations

ACID

Concurrency

Support for concurrent manipulation of data

yes

by using the rrdcached daemon

Durability

Support for making data persistent

yes

yes, using LMDB

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

User concepts

Access control

Planned for future releases

Access rights for users and roles

User authentification and security via Rexster Graph Server

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.