DBMS > EXASOL vs. FileMaker vs. RDF4J vs. Riak KV vs. RocksDB

System Properties Comparison EXASOL vs. FileMaker vs. RDF4J vs. Riak KV vs. RocksDB

Editorial information provided by DB-Engines

Name

Description

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

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

RDF4J is a Java framework for processing RDF data, supporting both memory-based and a disk-based storage.

Distributed, fault tolerant key-value store

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

Primary database model

Relational DBMS

RDF store

Key-value store

with links between data sets and object tags for the creation of secondary indexes

Key-value store

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

Score	2.25
Rank	#120	Overall
	#57	Relational DBMS

Score	49.73
Rank	#20	Overall
	#14	Relational DBMS

Score	0.71
Rank	#231	Overall
	#9	RDF stores

Score	4.44
Rank	#80	Overall
	#9	Key-value stores

Score	4.00
Rank	#84	Overall
	#11	Key-value stores

Website

www.exasol.com

www.claris.com/filemaker

rdf4j.org

rocksdb.org

Technical documentation

www.exasol.com/resources

www.claris.com/resources/documentation

rdf4j.org/documentation

www.tiot.jp/riak-docs/riak/kv/latest

github.com/facebook/rocksdb/wiki

Developer

Exasol

Claris

a subsidiary of Apple

Since 2016 officially forked into an Eclipse project, former developer was Aduna Software.

OpenSource, formerly Basho Technologies

Facebook, Inc.

Initial release

2000

1983

2004

2009

2013

Current release

19.4.1, November 2021

3.2.0, December 2022

8.11.4, April 2024

License

Commercial or Open Source

commercial

Open Source

Eclipse Distribution License (EDL), v1.0.

Open Source

Apache version 2, commercial enterprise edition

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

Erlang

C++

Server operating systems

iOS

client part only
Linux
OS X
Windows

Linux
OS X
Unix
Windows

Linux
OS X

Linux

Data scheme

yes

RDF Schemas

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

A http query request can return the data in XML format

Secondary indexes

yes

restricted

SQL

Support of SQL

yes

via plugins

APIs and other access methods

.Net
JDBC
ODBC
WebSocket

Filemaker WebDirect
JDBC
ODBC

Java API
RIO

RDF Input/Output
Sail API
SeRQL

Sesame RDF Query Language
Sesame REST HTTP Protocol
SPARQL

HTTP API
Native Erlang Interface

C++ API
Java API

Supported programming languages

Java
Lua
Python
R

PHP

Java
PHP
Python

unofficial client library
C#
C++

unofficial client library
Clojure

unofficial client library
Dart

unofficial client library
Erlang
Go

unofficial client library
Groovy

unofficial client library
Haskell

unofficial client library
Java
JavaScript

unofficial client library
Lisp

unofficial client library
Perl

unofficial client library
PHP
Python
Ruby
Scala

unofficial client library
Smalltalk

unofficial client library

C
C++
Go
Java
Perl
Python
Ruby

Server-side scripts

Stored procedures

user defined functions

yes

Erlang

Triggers

yes

pre-commit hooks and post-commit hooks

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

Sharding

no "single point of failure"

horizontal partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication, warm standby

since Version 14

none

selectable replication factor

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Hadoop integration

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency

Foreign keys

Referential integrity

yes

links between data sets can be stored

Transaction concepts

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

ACID

Isolation support depends on the API used

yes

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

in-memory storage is supported as well

yes

In-memory capabilities

Is there an option to define some or all structures to be held in-memory only.

yes

User concepts

Access control

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

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

yes, using Riak Security

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.