DBMS > EXASOL vs. FatDB vs. Google BigQuery vs. Quasardb vs. RDF4J

System Properties Comparison EXASOL vs. FatDB vs. Google BigQuery vs. Quasardb 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.

Description

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

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

Large scale data warehouse service with append-only tables

Distributed, high-performance timeseries database

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	1.76
Rank	#139	Overall
	#62	Relational DBMS

Score	58.10
Rank	#19	Overall
	#13	Relational DBMS

Score	0.21
Rank	#322	Overall
	#29	Time Series DBMS

Score	0.74
Rank	#222	Overall
	#9	RDF stores

Website

www.exasol.com

cloud.google.com/bigquery

quasar.ai

rdf4j.org

Technical documentation

www.exasol.com/resources

cloud.google.com/bigquery/docs

doc.quasar.ai/master

rdf4j.org/documentation

Developer

Exasol

FatCloud

Google

quasardb

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

Initial release

2000

2012

2010

2009

2004

Current release

3.14.1, January 2024

License

Commercial or Open Source

commercial

Free community edition, Non-profit organizations and non-commercial usage are eligible for free licenses

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++

Java

Server operating systems

Windows

hosted

BSD
Linux
OS X
Windows

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

integer and binary

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.

Secondary indexes

yes

with tags

yes

SQL

Support of SQL

yes

Via inetgration in SQL Server

yes

SQL-like query language

APIs and other access methods

.Net
JDBC
ODBC
WebSocket

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

RESTful HTTP/JSON API

HTTP API

Java API
RIO

RDF Input/Output
Sail API
SeRQL

Sesame RDF Query Language
Sesame REST HTTP Protocol
SPARQL

Supported programming languages

Java
Lua
Python
R

.Net
Java
JavaScript
Objective-C
PHP
Python
Ruby

.Net
C
C#
C++
Go
Java
JavaScript (Node.js)
PHP
Python
R

Java
PHP
Python

Server-side scripts

Stored procedures

user defined functions

yes

via applications

user defined functions

in JavaScript

yes

Triggers

yes

via applications

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

Sharding

consistent hashing

none

Replication methods

Methods for redundantly storing data on multiple nodes

selectable replication factor

Source-replica replication with selectable replication factor

none

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Hadoop integration

yes

with Hadoop integration

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency
Immediate Consistency

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

Since BigQuery is designed for querying data

ACID

Isolation support depends on the API used

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

by using LevelDB

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

Transient mode

User concepts

Access control

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

Can implement custom security layer via applications

Access privileges (owner, writer, reader) on dataset, table or view level

Google Cloud Identity & Access Management (IAM)

Cryptographically strong user authentication and audit trail

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.