DBMS > EXASOL vs. FatDB vs. Manticore Search vs. RDF4J vs. SAP HANA

System Properties Comparison EXASOL vs. FatDB vs. Manticore Search vs. RDF4J vs. SAP HANA

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.

Multi-storage database for search, including full-text search.

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

In-memory, column based data store. Available as appliance or cloud service

Primary database model

Relational DBMS

Document store
Key-value store

Search engine

RDF store

Relational DBMS

Secondary database models

Time Series DBMS

using the Manticore Columnar Library

Document store
Graph DBMS

with SAP Hana, Enterprise Edition
Spatial DBMS

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

Score	1.99
Rank	#124	Overall
	#58	Relational DBMS

Score	0.22
Rank	#312	Overall
	#21	Search engines

Score	0.69
Rank	#230	Overall
	#9	RDF stores

Score	44.69
Rank	#22	Overall
	#16	Relational DBMS

Website

www.exasol.com

manticoresearch.com

rdf4j.org

www.sap.com/products/hana.html

Technical documentation

www.exasol.com/resources

manual.manticoresearch.com

rdf4j.org/documentation

help.sap.com/hana

Developer

Exasol

FatCloud

Manticore Software

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

SAP

Initial release

2000

2012

2017

2004

2010

Current release

6.0, February 2023

2.0 SPS07 (April 4, 2023), April 2023

License

Commercial or Open Source

commercial

Open Source

GPL version 2

Open Source

Eclipse Distribution License (EDL), v1.0.

commercial

Cloud-based only

Only available as a cloud service

also available as a cloud based service

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

FreeBSD
Linux
macOS
Windows

Linux
OS X
Unix
Windows

Appliance or cloud-service

Data scheme

yes

schema-free

Fixed schema

yes

RDF Schemas

yes

Typing

predefined data types such as float or date

yes

Int, Bigint, Float, Timestamp, Bit, Int array, Bigint array, JSON, Boolean

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.

Can index from XML

Secondary indexes

yes

full-text index on all search fields

yes

SQL

Support of SQL

yes

Via inetgration in SQL Server

SQL-like query language

yes

APIs and other access methods

.Net
JDBC
ODBC
WebSocket

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

Binary API
RESTful HTTP/JSON API
RESTful HTTP/SQL API
SQL over MySQL

Java API
RIO

RDF Input/Output
Sail API
SeRQL

Sesame RDF Query Language
Sesame REST HTTP Protocol
SPARQL

JDBC
ODBC

Supported programming languages

Java
Lua
Python
R

Elixir
Go
Java
JavaScript (Node.js)
Perl
PHP
Python

Java
PHP
Python

Server-side scripts

Stored procedures

user defined functions

yes

via applications

user defined functions

yes

SQLScript, R

Triggers

yes

via applications

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

Partitioning is done manually, search queries against distributed index is supported

none

yes

Replication methods

Methods for redundantly storing data on multiple nodes

selectable replication factor

Synchronous replication based on Galera library

none

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
Immediate Consistency

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

yes

isolated transactions for atomic changes and binary logging for safe writes

ACID

Isolation support depends on the API used

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

The original contents of fields are not stored in the Manticore index.

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

Can implement custom security layer via applications

yes

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.