DBMS > FatDB vs. GridDB vs. InterSystems Caché vs. SAP HANA

System Properties Comparison FatDB vs. GridDB vs. InterSystems Caché vs. SAP HANA

Please select another system to include it in the comparison.

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.

Caché is a deprecated database engine which is substituted with InterSystems IRIS. It therefore is removed from the DB-Engines Ranking.

Description

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

Scalable in-memory time series database optimized for IoT and Big Data

A multi-model DBMS and application server

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

Primary database model

Document store
Key-value store

Time Series DBMS

Key-value store
Object oriented DBMS
Relational DBMS

Relational DBMS

Secondary database models

Key-value store
Relational DBMS

Document store

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.91
Rank	#123	Overall
	#10	Time Series DBMS

Score	41.32
Rank	#23	Overall
	#16	Relational DBMS

Website

griddb.net

www.intersystems.com/products/cache

www.sap.com/products/hana.html

Technical documentation

docs.griddb.net

docs.intersystems.com

help.sap.com/hana

Developer

FatCloud

Toshiba Corporation

InterSystems

SAP

Initial release

2012

2013

1997

2010

Current release

5.1, August 2022

2018.1.4, May 2020

2.0 SPS07 (April 4, 2023), April 2023

License

Commercial or Open Source

commercial

Open Source

AGPL version 3 and Apache License, version 2.0 , commercial license (standard and advanced editions) also available

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

Server operating systems

Windows

Linux

AIX
HP Open VMS
HP-UX
Linux
OS X
Solaris
Windows

Appliance or cloud-service

Data scheme

schema-free

yes

depending on used data model

yes

Typing

predefined data types such as float or date

yes

numerical, string, blob, geometry, boolean, timestamp

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

Secondary indexes

yes

SQL

Support of SQL

Via inetgration in SQL Server

SQL92, SQL-like TQL (Toshiba Query Language)

yes

APIs and other access methods

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

JDBC
ODBC
Proprietary protocol
RESTful HTTP/JSON API

.NET Client API
JDBC
ODBC
RESTful HTTP API

JDBC
ODBC

Supported programming languages

C
C++
Go
Java
JavaScript (Node.js)
Perl
PHP
Python
Ruby

C#
C++
Java

Server-side scripts

Stored procedures

yes

via applications

yes

SQLScript, R

Triggers

yes

via applications

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

yes

Replication methods

Methods for redundantly storing data on multiple nodes

selectable replication factor

Source-replica replication

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Connector for using GridDB as an input source and output destination for Hadoop MapReduce jobs

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency
Immediate Consistency

Immediate consistency within container, eventual consistency across containers

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID at container level

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

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

Can implement custom security layer via applications

Access rights for users can be defined per database

Access rights for users, groups and roles

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.