DBMS > Faircom DB vs. HugeGraph vs. InterSystems Caché vs. SAP HANA

System Properties Comparison Faircom DB vs. HugeGraph vs. InterSystems Caché vs. SAP HANA

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

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

Description

Native high-speed multi-model DBMS for relational and key-value store data simultaneously accessible through SQL and NoSQL APIs.

A fast-speed and highly-scalable Graph DBMS

A multi-model DBMS and application server

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

Primary database model

Key-value store
Relational DBMS

Graph DBMS

Key-value store
Object oriented DBMS
Relational DBMS

Relational DBMS

Secondary database models

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	0.29
Rank	#304	Overall
	#43	Key-value stores
	#136	Relational DBMS

Score	0.17
Rank	#335	Overall
	#31	Graph DBMS

Score	44.27
Rank	#23	Overall
	#16	Relational DBMS

Website

www.faircom.com/products/faircom-db

github.com/hugegraph
hugegraph.apache.org

www.intersystems.com/products/cache

www.sap.com/products/hana.html

Technical documentation

docs.faircom.com/docs/en/UUID-7446ae34-a1a7-c843-c894-d5322e395184.html

hugegraph.apache.org/docs

docs.intersystems.com

help.sap.com/hana

Developer

FairCom Corporation

Baidu

InterSystems

SAP

Initial release

1979

2018

1997

2010

Current release

V12, November 2020

0.9

2018.1.4, May 2020

2.0 SPS07 (April 4, 2023), April 2023

License

Commercial or Open Source

commercial

Restricted, free version available

Open Source

Apache Version 2.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

ANSI C, C++

Java

Server operating systems

AIX
FreeBSD
HP-UX
Linux
NetBSD
OS X
QNX
SCO
Solaris
VxWorks
Windows

easily portable to other OSs

Linux
macOS
Unix

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

Appliance or cloud-service

Data scheme

schema free, schema optional, schema required, partial schema,

yes

depending on used data model

yes

Typing

predefined data types such as float or date

yes, ANSI SQL Types, JSON, typed binary structures

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

also supports composite index and range index

yes

SQL

Support of SQL

yes, ANSI SQL with proprietary extensions

yes

APIs and other access methods

ADO.NET
Direct SQL
JDBC
JPA
ODBC
RESTful HTTP/JSON API
RESTful MQTT/JSON API
RPC

Java API
RESTful HTTP API
TinkerPop Gremlin

.NET Client API
JDBC
ODBC
RESTful HTTP API

JDBC
ODBC

Supported programming languages

.Net
C
C#
C++
Java
JavaScript (Node.js and browser)
PHP
Python
Visual Basic

Groovy
Java
Python

C#
C++
Java

Server-side scripts

Stored procedures

yes

.Net, JavaScript, C/C++

asynchronous Gremlin script jobs

yes

SQLScript, R

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

File partitioning, horizontal partitioning, sharding

Customizable business rules for table partitioning

yes

depending on used storage backend, e.g. Cassandra and HBase

none

yes

Replication methods

Methods for redundantly storing data on multiple nodes

yes, configurable to be parallel or serial, synchronous or asynchronous, uni-directional or bi-directional, ACID-consistent or eventually consistent (with custom conflict resolution).

yes

depending on used storage backend, e.g. Cassandra and HBase

Source-replica replication

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

via hugegraph-spark

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency
Immediate Consistency
Tunable consistency per server, database, table, and transaction

Eventual Consistency

Immediate Consistency

Foreign keys

Referential integrity

yes

edges in graph

yes

Transaction concepts

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

tunable from ACID to Eventually Consistent

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

Yes, tunable from durable to delayed durability to in-memory

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

Fine grained access rights according to SQL-standard with additional protections for files

Users, roles and permissions

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.