DBMS > Faircom DB vs. JanusGraph vs. Realm vs. SAP HANA

System Properties Comparison Faircom DB vs. JanusGraph vs. Realm vs. SAP HANA

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Native high-speed multi-model DBMS for relational and key-value store data simultaneously accessible through SQL and NoSQL APIs.

A Graph DBMS optimized for distributed clusters

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

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

In-memory, column based data store. Available as appliance or cloud service

Primary database model

Key-value store
Relational DBMS

Graph DBMS

Document store

Relational DBMS

Secondary database models

Document store
Graph DBMS

with SAP Hana, Enterprise Edition
Spatial DBMS

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

Score	0.20
Rank	#318	Overall
	#48	Key-value stores
	#141	Relational DBMS

Score	1.94
Rank	#129	Overall
	#12	Graph DBMS

Score	7.60
Rank	#52	Overall
	#9	Document stores

Score	44.69
Rank	#22	Overall
	#16	Relational DBMS

Website

www.faircom.com/products/faircom-db

janusgraph.org

realm.io

www.sap.com/products/hana.html

Technical documentation

docs.faircom.com/docs/en/UUID-7446ae34-a1a7-c843-c894-d5322e395184.html

docs.janusgraph.org

realm.io/docs

help.sap.com/hana

Developer

FairCom Corporation

Linux Foundation; originally developed as Titan by Aurelius

Realm, acquired by MongoDB in May 2019

SAP

Initial release

1979

2017

2014

2010

Current release

V12, November 2020

0.6.3, February 2023

2.0 SPS07 (April 4, 2023), April 2023

License

Commercial or Open Source

commercial

Restricted, free version available

Open Source

Apache 2.0

Open Source

commercial

Cloud-based only

Only available as a cloud service

also available as a cloud based service

DBaaS offerings (sponsored links)

Database as a Service

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

Implementation language

ANSI C, C++

Java

Server operating systems

AIX
FreeBSD
HP-UX
Linux
NetBSD
OS X
QNX
SCO
Solaris
VxWorks
Windows

easily portable to other OSs

Linux
OS X
Unix
Windows

Android
Backend: server-less
iOS
Windows

Appliance or cloud-service

Data scheme

schema free, schema optional, schema required, partial schema,

yes

Typing

predefined data types such as float or date

yes, ANSI SQL Types, JSON, typed binary structures

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

SQL

Support of SQL

yes, ANSI SQL with proprietary extensions

yes

APIs and other access methods

ADO.NET
Direct SQL
JDBC
JPA
ODBC
RESTful HTTP/JSON API
RESTful MQTT/JSON API
RPC

Java API
TinkerPop Blueprints
TinkerPop Frames
TinkerPop Gremlin
TinkerPop Rexster

JDBC
ODBC

Supported programming languages

.Net
C
C#
C++
Java
JavaScript (Node.js and browser)
PHP
Python
Visual Basic

Clojure
Java
Python

.Net
Java

with Android only
Objective-C
React Native
Swift

Server-side scripts

Stored procedures

yes

.Net, JavaScript, C/C++

yes

runs within the applications so server-side scripts are unnecessary

SQLScript, R

Triggers

yes

Change Listeners

yes

Partitioning methods

Methods for storing different data on different nodes

File partitioning, horizontal partitioning, sharding

Customizable business rules for table partitioning

yes

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

none

yes

Replication methods

Methods for redundantly storing data on multiple nodes

yes, configurable to be parallel or serial, synchronous or asynchronous, uni-directional or bi-directional, ACID-consistent or eventually consistent (with custom conflict resolution).

yes

none

yes

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

Eventual Consistency
Immediate Consistency
Tunable consistency per server, database, table, and transaction

Eventual Consistency
Immediate Consistency

Immediate Consistency

Foreign keys

Referential integrity

yes

Relationships in graphs

yes

Transaction concepts

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

tunable from ACID to Eventually Consistent

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

Yes, tunable from durable to delayed durability to in-memory

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

Fine grained access rights according to SQL-standard with additional protections for files

User authentification and security via Rexster Graph Server

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.