DBMS > Datomic vs. FileMaker vs. InterSystems Caché vs. RocksDB vs. TerminusDB

System Properties Comparison Datomic vs. FileMaker vs. InterSystems Caché vs. RocksDB vs. TerminusDB

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

FileMaker is a cross-platform RDBMS that includes a GUI frontend.

A multi-model DBMS and application server

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

Scalable Graph Database platform making enterprise data available by exploiting inferred entities and relationships

Primary database model

Relational DBMS

Key-value store
Object oriented DBMS
Relational DBMS

Key-value store

Graph DBMS

Secondary database models

Document store

Document store
RDF store

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

Score	1.59
Rank	#150	Overall
	#69	Relational DBMS

Score	48.20
Rank	#20	Overall
	#14	Relational DBMS

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

Score	0.17
Rank	#325	Overall
	#29	Graph DBMS

Website

www.datomic.com

www.claris.com/filemaker

www.intersystems.com/products/cache

rocksdb.org

terminusdb.com

Technical documentation

docs.datomic.com

www.claris.com/resources/documentation

docs.intersystems.com

github.com/facebook/rocksdb/wiki

terminusdb.github.io/terminusdb/#

Developer

Cognitect

Claris

a subsidiary of Apple

InterSystems

Facebook, Inc.

DataChemist Ltd.

Initial release

2012

1983

1997

2013

2018

Current release

1.0.6735, June 2023

19.4.1, November 2021

2018.1.4, May 2020

8.11.4, April 2024

11.0.0, January 2023

License

Commercial or Open Source

commercial

limited edition free

commercial

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

C++

Prolog, Rust

Server operating systems

All OS with a Java VM

iOS

client part only
Linux
OS X
Windows

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

Linux

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

A http query request can return the data in XML format

yes

Secondary indexes

yes

SQL

Support of SQL

yes

via plugins

yes

SQL-like query language (WOQL)

APIs and other access methods

RESTful HTTP API

Filemaker WebDirect
JDBC
ODBC

.NET Client API
JDBC
ODBC
RESTful HTTP API

C++ API
Java API

OWL
RESTful HTTP API
WOQL (Web Object Query Language)

Supported programming languages

Clojure
Java

PHP

C#
C++
Java

C
C++
Go
Java
Perl
Python
Ruby

JavaScript
Python

Server-side scripts

Stored procedures

yes

Transaction Functions

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

horizontal partitioning

Graph Partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

none

But extensive use of caching in the application peers

Source-replica replication, warm standby

since Version 14

Source-replica replication

yes

Journaling Streams

MapReduce

Offers an API for user-defined Map/Reduce methods

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

yes

ACID

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 journaling

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

simple rights management via user accounts and connection to external directory services

Access rights for users, groups and roles

Role-based access control

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.