DBMS > Datomic vs. Dgraph vs. Faircom DB vs. RocksDB vs. SWC-DB

System Properties Comparison Datomic vs. Dgraph vs. Faircom DB vs. RocksDB vs. SWC-DB

Editorial information provided by DB-Engines

Name

Description

Datomic builds on immutable values, supports point-in-time queries and uses 3rd party systems for durability

Distributed and scalable native Graph DBMS

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

Embeddable persistent key-value store optimized for fast storage (flash and RAM)

A high performance, scalable Wide Column DBMS

Primary database model

Relational DBMS

Graph DBMS

Key-value store
Relational DBMS

Key-value store

Wide column store

Secondary database models

Time Series DBMS

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

Score	1.66
Rank	#144	Overall
	#66	Relational DBMS

Score	1.53
Rank	#152	Overall
	#15	Graph DBMS

Score	0.29
Rank	#304	Overall
	#43	Key-value stores
	#136	Relational DBMS

Score	3.41
Rank	#86	Overall
	#11	Key-value stores

Score	0.08
Rank	#364	Overall
	#13	Wide column stores

Website

www.datomic.com

dgraph.io

www.faircom.com/products/faircom-db

rocksdb.org

github.com/kashirin-alex/swc-db
www.swcdb.org

Technical documentation

docs.datomic.com

dgraph.io/docs

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

github.com/facebook/rocksdb/wiki

Developer

Cognitect

Dgraph Labs, Inc.

FairCom Corporation

Facebook, Inc.

Alex Kashirin

Initial release

2012

2016

1979

2013

2020

Current release

1.0.7075, December 2023

V12, November 2020

9.2.1, May 2024

0.5, April 2021

License

Commercial or Open Source

commercial

limited edition free

Open Source

Apache 2.0

commercial

Restricted, free version available

Open Source

BSD

Open Source

GPL V3

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

Java, Clojure

ANSI C, C++

C++

Server operating systems

All OS with a Java VM

Linux
OS X
Windows

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

easily portable to other OSs

Linux

Data scheme

yes

schema-free

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

schema-free

Typing

predefined data types such as float or date

yes

yes, ANSI SQL Types, JSON, typed binary structures

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

SQL-like query language

APIs and other access methods

RESTful HTTP API

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

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

C++ API
Java API

Proprietary protocol
Thrift

Supported programming languages

Clojure
Java

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

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

C
C++
Go
Java
Perl
Python
Ruby

C++

Server-side scripts

Stored procedures

yes

Transaction Functions

yes

.Net, JavaScript, C/C++

Triggers

By using transaction functions

yes

Partitioning methods

Methods for storing different data on different nodes

none

But extensive use of caching in the application peers

yes

File partitioning, horizontal partitioning, sharding

Customizable business rules for table partitioning

horizontal partitioning

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

none

But extensive use of caching in the application peers

Synchronous replication via Raft

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

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

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

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

tunable from ACID to Eventually Consistent

yes

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

using external storage systems (e.g. Cassandra, DynamoDB, PostgreSQL, Couchbase and others)

yes

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

yes

In-memory capabilities

Is there an option to define some or all structures to be held in-memory only.

yes

recommended only for testing and development

yes

User concepts

Access control

Planned for future releases

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

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.