DBMS > Citus vs. Datomic vs. MarkLogic vs. RocksDB

System Properties Comparison Citus vs. Datomic vs. MarkLogic vs. RocksDB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Scalable hybrid operational and analytics RDBMS for big data use cases based on PostgreSQL

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

Operational and transactional Enterprise NoSQL database

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

Primary database model

Relational DBMS

Document store
Native XML DBMS
RDF store

as of version 7
Search engine

Key-value store

Secondary database models

Document store

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

Score	2.21
Rank	#118	Overall
	#56	Relational DBMS

Score	1.59
Rank	#150	Overall
	#69	Relational DBMS

Score	5.92
Rank	#58	Overall
	#10	Document stores
	#1	Native XML DBMS
	#1	RDF stores
	#6	Search engines

Score	3.65
Rank	#85	Overall
	#11	Key-value stores

Website

Technical documentation

docs.citusdata.com

docs.datomic.com

docs.marklogic.com

github.com/facebook/rocksdb/wiki

Developer

Cognitect

MarkLogic Corp.

Facebook, Inc.

Initial release

2010

2012

2001

2013

Current release

8.1, December 2018

1.0.6735, June 2023

11.0, December 2022

8.11.4, April 2024

License

Commercial or Open Source

Open Source

AGPL, commercial license also available

commercial

limited edition free

commercial

restricted free version is available

Open Source

BSD

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

C++

Server operating systems

Linux

All OS with a Java VM

Linux
OS X
Windows

Linux

Data scheme

yes

schema-free

Schema can be enforced

schema-free

Typing

predefined data types such as float or date

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.

yes

specific XML type available, but no XML query functionality

yes

Secondary indexes

yes

SQL

Support of SQL

yes

standard, with numerous extensions

yes

SQL92

APIs and other access methods

ADO.NET
JDBC
native C library
ODBC
streaming API for large objects

RESTful HTTP API

Java API
Node.js Client API
ODBC
proprietary Optic API

Proprietary Query API, introduced with version 9
RESTful HTTP API
SPARQL
WebDAV
XDBC
XQuery
XSLT

C++ API
Java API

Supported programming languages

.Net
C
C++
Delphi
Java
JavaScript (Node.js)
Perl
PHP
Python
Tcl

Clojure
Java

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

C
C++
Go
Java
Perl
Python
Ruby

Server-side scripts

Stored procedures

user defined functions

realized in proprietary language PL/pgSQL or with common languages like Perl, Python, Tcl etc.

yes

Transaction Functions

yes

via XQuery or JavaScript

Triggers

yes

By using transaction functions

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

But extensive use of caching in the application peers

Sharding

horizontal partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

other methods possible by using 3rd party extensions

none

But extensive use of caching in the application peers

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

via Hadoop Connector, HDFS Direct Access and in-database MapReduce jobs

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

can act as a resource manager in an XA/JTA transaction

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

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, with Range Indexes

yes

User concepts

Access control

fine grained access rights according to SQL-standard

Role-based access control at the document and subdocument levels

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.