DBMS > Datomic vs. Interbase vs. InterSystems Caché vs. JaguarDB vs. RocksDB

System Properties Comparison Datomic vs. Interbase vs. InterSystems Caché vs. JaguarDB vs. RocksDB

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

Light-weight proven RDBMS

originally from Borland

A multi-model DBMS and application server

Performant, highly scalable DBMS for AI and IoT applications

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

Primary database model

Relational DBMS

Key-value store
Object oriented DBMS
Relational DBMS

Key-value store
Vector DBMS

Key-value store

Secondary database models

Document store

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

Score	1.59
Rank	#150	Overall
	#69	Relational DBMS

Score	4.61
Rank	#72	Overall
	#39	Relational DBMS

Score	0.00
Rank	#383	Overall
	#60	Key-value stores
	#13	Vector DBMS

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

Website

www.datomic.com

www.embarcadero.com/products/interbase

www.intersystems.com/products/cache

www.jaguardb.com

rocksdb.org

Technical documentation

docs.datomic.com

docs.embarcadero.com/products/interbase

docs.intersystems.com

www.jaguardb.com/support.html

github.com/facebook/rocksdb/wiki

Developer

Cognitect

Embarcadero

InterSystems

DataJaguar, Inc.

Facebook, Inc.

Initial release

2012

1984

1997

2015

2013

Current release

1.0.6735, June 2023

InterBase 2020, December 2019

2018.1.4, May 2020

3.3 July 2023

8.11.4, April 2024

License

Commercial or Open Source

commercial

limited edition free

commercial

Open Source

GPL V3.0

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++

the server part. Clients available in other languages

C++

Server operating systems

All OS with a Java VM

Android
iOS
Linux
OS X
Windows

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

Linux

Data scheme

yes

depending on used data model

yes

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.

export as XML data possible

yes

Secondary indexes

yes

SQL

Support of SQL

yes

A subset of ANSI SQL is implemented

but no views, foreign keys, triggers

APIs and other access methods

RESTful HTTP API

ADO.NET
JDBC
ODBC

.NET Client API
JDBC
ODBC
RESTful HTTP API

JDBC
ODBC

C++ API
Java API

Supported programming languages

Clojure
Java

.Net
C
C++
Delphi
Java
Object Pascal
PHP
Ruby

C#
C++
Java

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

C
C++
Go
Java
Perl
Python
Ruby

Server-side scripts

Stored procedures

yes

Transaction Functions

yes

Interbase procedure and trigger language

yes

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

none

Sharding

horizontal partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

none

But extensive use of caching in the application peers

Interbase Change Views

Source-replica replication

Multi-source replication

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

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

yes

Concurrency

Support for concurrent manipulation of data

yes

Multiversion concurreny control

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

User concepts

Access control

fine grained access rights according to SQL-standard

Access rights for users, groups and roles

rights management via user accounts

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.