DBMS > Datomic vs. EXASOL vs. InterSystems Caché vs. RocksDB vs. Vitess

System Properties Comparison Datomic vs. EXASOL vs. InterSystems Caché vs. RocksDB vs. Vitess

Editorial information provided by DB-Engines

Name

Caché is a deprecated database engine which is substituted with InterSystems IRIS. It therefore is removed from the DB-Engines Ranking.

Description

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

High-performance, in-memory, MPP database specifically designed for in-memory analytics.

A multi-model DBMS and application server

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

Scalable, distributed, cloud-native DBMS, extending MySQL

Primary database model

Relational DBMS

Key-value store
Object oriented DBMS
Relational DBMS

Key-value store

Relational DBMS

Secondary database models

Document store

Document store
Spatial DBMS

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

Score	1.59
Rank	#150	Overall
	#69	Relational DBMS

Score	1.99
Rank	#124	Overall
	#58	Relational DBMS

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

Score	0.82
Rank	#209	Overall
	#97	Relational DBMS

Website

www.datomic.com

www.exasol.com

www.intersystems.com/products/cache

rocksdb.org

vitess.io

Technical documentation

docs.datomic.com

www.exasol.com/resources

docs.intersystems.com

github.com/facebook/rocksdb/wiki

vitess.io/docs

Developer

Cognitect

Exasol

InterSystems

Facebook, Inc.

The Linux Foundation, PlanetScale

Initial release

2012

2000

1997

2013

Current release

1.0.6735, June 2023

2018.1.4, May 2020

8.11.4, April 2024

15.0.2, December 2022

License

Commercial or Open Source

commercial

limited edition free

commercial

Open Source

BSD

Open Source

Apache Version 2.0, commercial licenses available

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

All OS with a Java VM

AIX
HP Open VMS
HP-UX
Linux
OS X
Solaris
Windows

Linux

Docker
Linux
macOS

Data scheme

yes

depending on used data model

schema-free

yes

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

Secondary indexes

yes

SQL

Support of SQL

yes

with proprietary extensions

APIs and other access methods

RESTful HTTP API

.Net
JDBC
ODBC
WebSocket

.NET Client API
JDBC
ODBC
RESTful HTTP API

C++ API
Java API

ADO.NET
JDBC
MySQL protocol
ODBC

Supported programming languages

Clojure
Java

Java
Lua
Python
R

C#
C++
Java

C
C++
Go
Java
Perl
Python
Ruby

Ada
C
C#
C++
D
Delphi
Eiffel
Erlang
Haskell
Java
JavaScript (Node.js)
Objective-C
OCaml
Perl
PHP
Python
Ruby
Scheme
Tcl

Server-side scripts

Stored procedures

yes

Transaction Functions

user defined functions

yes

proprietary syntax

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

Sharding

none

horizontal partitioning

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

none

But extensive use of caching in the application peers

Source-replica replication

yes

Multi-source replication
Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Hadoop integration

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency across shards
Immediate Consistency within a shard

Foreign keys

Referential integrity

yes

not for MyISAM storage engine

Transaction concepts

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

ACID

yes

ACID at shard level

Concurrency

Support for concurrent manipulation of data

yes

table locks or row locks depending on storage engine

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

User concepts

Access control

Access rights for users, groups and roles according to SQL-standard

Access rights for users, groups and roles

Users with fine-grained authorization concept

no user groups or roles

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.