DBMS > Amazon Redshift vs. FatDB vs. FileMaker vs. IRONdb vs. RDF4J

System Properties Comparison Amazon Redshift vs. FatDB vs. FileMaker vs. IRONdb vs. RDF4J

Editorial information provided by DB-Engines

Name

FatDB/FatCloud has ceased operations as a company with February 2014. FatDB is discontinued and excluded from the ranking.

IRONdb seems to be discontinued. Therefore it is excluded from the DB-Engines Ranking.

Description

Large scale data warehouse service for use with business intelligence tools

A .NET NoSQL DBMS that can integrate with and extend SQL Server.

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

A distributed Time Series DBMS with a focus on scalability, fault tolerance and operational simplicity

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

Primary database model

Relational DBMS

Document store
Key-value store

Relational DBMS

Time Series DBMS

RDF store

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

Score	17.94
Rank	#34	Overall
	#21	Relational DBMS

Score	48.20
Rank	#20	Overall
	#14	Relational DBMS

Score	0.69
Rank	#230	Overall
	#9	RDF stores

Website

aws.amazon.com/redshift

www.claris.com/filemaker

www.circonus.com/solutions/time-series-database/

rdf4j.org

Technical documentation

docs.aws.amazon.com/redshift

www.claris.com/resources/documentation

docs.circonus.com/irondb/category/getting-started

rdf4j.org/documentation

Developer

Amazon (based on PostgreSQL)

FatCloud

Claris

a subsidiary of Apple

Circonus LLC.

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

Initial release

2012

1983

2017

2004

Current release

19.4.1, November 2021

V0.10.20, January 2018

License

Commercial or Open Source

commercial

Open Source

Eclipse Distribution License (EDL), v1.0.

Cloud-based only

Only available as a cloud service

yes

DBaaS offerings (sponsored links)

Database as a Service

Providers of DBaaS offerings, please contact us to be listed.

Implementation language

C and C++

Java

Server operating systems

hosted

Windows

iOS

client part only
Linux
OS X
Windows

Linux

Linux
OS X
Unix
Windows

Data scheme

yes

schema-free

yes

schema-free

yes

RDF Schemas

Typing

predefined data types such as float or date

yes

text, numeric, histograms

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

restricted

yes

SQL

Support of SQL

yes

does not fully support an SQL-standard

Via inetgration in SQL Server

yes

via plugins

SQL-like query language (Circonus Analytics Query Language: CAQL)

APIs and other access methods

JDBC
ODBC

.NET Client API
LINQ
RESTful HTTP API
RPC
Windows WCF Bindings

Filemaker WebDirect
JDBC
ODBC

HTTP API

Java API
RIO

RDF Input/Output
Sail API
SeRQL

Sesame RDF Query Language
Sesame REST HTTP Protocol
SPARQL

Supported programming languages

All languages supporting JDBC/ODBC

PHP

.Net
C
C++
Clojure
Erlang
Go
Haskell
Java
JavaScript
JavaScript (Node.js)
Lisp
Lua
Perl
PHP
Python
R
Ruby
Rust
Scala

Java
PHP
Python

Server-side scripts

Stored procedures

user defined functions

in Python

yes

via applications

yes

yes, in Lua

yes

Triggers

yes

via applications

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

Automatic, metric affinity per node

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes

selectable replication factor

Source-replica replication, warm standby

since Version 14

configurable replication factor, datacenter aware

none

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency
Immediate Consistency

Immediate consistency per node, eventual consistency across nodes

Foreign keys

Referential integrity

yes

informational only, not enforced by the system

yes

Transaction concepts

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

ACID

Isolation support depends on the API used

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

in-memory storage is supported as well

In-memory capabilities

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

yes

User concepts

Access control

fine grained access rights according to SQL-standard

Can implement custom security layer via applications

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

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.