DBMS > FileMaker vs. Geode vs. Heroic vs. RocksDB vs. XTDB

System Properties Comparison FileMaker vs. Geode vs. Heroic vs. RocksDB vs. XTDB

Editorial information provided by DB-Engines

Name

Description

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

Geode is a distributed data container, pooling memory, CPU, network resources, and optionally local disk across multiple processes

Time Series DBMS built at Spotify based on Cassandra or Google Cloud Bigtable, and ElasticSearch

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

A general purpose database with bitemporal SQL and Datalog and graph queries

Primary database model

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

Score	48.20
Rank	#20	Overall
	#14	Relational DBMS

Score	1.92
Rank	#131	Overall
	#23	Key-value stores

Score	0.51
Rank	#255	Overall
	#21	Time Series DBMS

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

Score	0.11
Rank	#343	Overall
	#46	Document stores

Website

www.claris.com/filemaker

geode.apache.org

github.com/spotify/heroic

rocksdb.org

github.com/xtdb/xtdb
www.xtdb.com

Technical documentation

www.claris.com/resources/documentation

geode.apache.org/docs

spotify.github.io/heroic

github.com/facebook/rocksdb/wiki

www.xtdb.com/docs

Developer

Claris

a subsidiary of Apple

Originally developed by Gemstone. They outsourced the project to Apache in 2015 but still deliver a commercial version as Gemfire.

Spotify

Facebook, Inc.

Juxt Ltd.

Initial release

1983

2002

2014

2013

2019

Current release

19.4.1, November 2021

1.1, February 2017

8.11.4, April 2024

1.19, September 2021

License

Commercial or Open Source

commercial

Open Source

Apache Version 2; commercial licenses available as Gemfire

Open Source

Apache 2.0

Open Source

BSD

Open Source

MIT License

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

C++

Clojure

Server operating systems

iOS

client part only
Linux
OS X
Windows

All OS with a Java VM

the JDK (8 or later) is also required

Linux

All OS with a Java 8 (and higher) VM
Linux

Data scheme

yes

schema-free

Typing

predefined data types such as float or date

yes

yes, extensible-data-notation format

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

via Elasticsearch

yes

SQL

Support of SQL

yes

via plugins

SQL-like query language (OQL)

limited SQL, making use of Apache Calcite

APIs and other access methods

Filemaker WebDirect
JDBC
ODBC

Java Client API
Memcached protocol
RESTful HTTP API

HQL (Heroic Query Language, a JSON-based language)
HTTP API

C++ API
Java API

HTTP REST
JDBC

Supported programming languages

PHP

.Net
All JVM based languages
C++
Groovy
Java
Scala

C
C++
Go
Java
Perl
Python
Ruby

Clojure
Java

Server-side scripts

Stored procedures

yes

user defined functions

Triggers

yes

Cache Event Listeners

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

horizontal partitioning

none

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication, warm standby

since Version 14

Multi-source replication

yes

yes, each node contains all data

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency

Eventual Consistency
Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

yes, on a single node

yes

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

yes, flexibel persistency by using storage technologies like Apache Kafka, RocksDB or LMDB

In-memory capabilities

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

yes

User concepts

Access control

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

Access rights per client and object definable

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.