DBMS > Datomic vs. InterSystems Caché vs. Oracle vs. Oracle Berkeley DB vs. RocksDB

System Properties Comparison Datomic vs. InterSystems Caché vs. Oracle vs. Oracle Berkeley DB 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

A multi-model DBMS and application server

Widely used RDBMS

Widely used in-process key-value store

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

Relational DBMS

Key-value store

supports sorted and unsorted key sets
Native XML DBMS

in the Oracle Berkeley DB XML version

Key-value store

Secondary database models

Document store

Document store
Graph DBMS

with Oracle Spatial and Graph
RDF store

with Oracle Spatial and Graph
Spatial DBMS

with Oracle Spatial and Graph
Vector DBMS

since Oracle 23

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

Score	1.59
Rank	#150	Overall
	#69	Relational DBMS

Score	1236.29
Rank	#1	Overall
	#1	Relational DBMS

Score	2.21
Rank	#117	Overall
	#20	Key-value stores
	#3	Native XML DBMS

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

Website

www.datomic.com

www.intersystems.com/products/cache

www.oracle.com/database

www.oracle.com/database/technologies/related/berkeleydb.html

rocksdb.org

Technical documentation

docs.datomic.com

docs.intersystems.com

docs.oracle.com/en/database

docs.oracle.com/cd/E17076_05/html/index.html

github.com/facebook/rocksdb/wiki

Developer

Cognitect

InterSystems

Oracle

originally developed by Sleepycat, which was acquired by Oracle

Facebook, Inc.

Initial release

2012

1997

1980

1994

2013

Current release

1.0.6735, June 2023

2018.1.4, May 2020

23c, September 2023

18.1.40, May 2020

9.2.1, May 2024

License

Commercial or Open Source

commercial

limited edition free

commercial

restricted free version is available

Open Source

commercial license 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 and C++

C, Java, C++ (depending on the Berkeley DB edition)

C++

Server operating systems

All OS with a Java VM

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

AIX
HP-UX
Linux
OS X
Solaris
Windows
z/OS

AIX
Android
FreeBSD
iOS
Linux
OS X
Solaris
VxWorks
Windows

Linux

Data scheme

yes

depending on used data model

yes

Schemaless in JSON and XML columns

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

only with the Berkeley DB XML edition

Secondary indexes

yes

SQL

Support of SQL

yes

with proprietary extensions

yes

SQL interfaced based on SQLite is available

APIs and other access methods

RESTful HTTP API

.NET Client API
JDBC
ODBC
RESTful HTTP API

JDBC
ODBC
ODP.NET
Oracle Call Interface (OCI)

C++ API
Java API

Supported programming languages

Clojure
Java

C#
C++
Java

C
C#
C++
Clojure
Cobol
Delphi
Eiffel
Erlang
Fortran
Groovy
Haskell
Java
JavaScript
Lisp
Objective C
OCaml
Perl
PHP
Python
R
Ruby
Scala
Tcl
Visual Basic

.Net

Figaro is a .Net framework assembly that extends Berkeley DB XML into an embeddable database engine for .NET
others

Third-party libraries to manipulate Berkeley DB files are available for many languages
C
C#
C++
Java
JavaScript (Node.js)

3rd party binding
Perl
Python
Tcl

C
C++
Go
Java
Perl
Python
Ruby

Server-side scripts

Stored procedures

yes

Transaction Functions

yes

PL/SQL

also stored procedures in Java possible

Triggers

By using transaction functions

yes

only for the SQL API

Partitioning methods

Methods for storing different data on different nodes

none

But extensive use of caching in the application peers

none

Sharding, horizontal partitioning

none

horizontal partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

none

But extensive use of caching in the application peers

Source-replica replication

Multi-source replication
Source-replica replication

Source-replica replication

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

can be realized in PL/SQL

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

isolation level can be parameterized

ACID

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

Version 12c introduced the new option 'Oracle Database In-Memory'

yes

User concepts

Access control

Access rights for users, groups and roles

fine grained access rights according to SQL-standard

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.