DBMS > Faircom DB vs. GigaSpaces vs. InterSystems Caché vs. Microsoft Azure Cosmos DB vs. Microsoft Azure Table Storage

System Properties Comparison Faircom DB vs. GigaSpaces vs. InterSystems Caché vs. Microsoft Azure Cosmos DB vs. Microsoft Azure Table Storage

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.

High performance in-memory data grid platform, powering three products: Smart Cache, Smart ODS (Operational Data Store), Smart Augmented Transactions

A multi-model DBMS and application server

Globally distributed, horizontally scalable, multi-model database service

A Wide Column Store for rapid development using massive semi-structured datasets

Primary database model

Key-value store
Relational DBMS

Document store
Object oriented DBMS

Values are user defined objects

Key-value store
Object oriented DBMS
Relational DBMS

Document store
Graph DBMS
Key-value store
Wide column store

Wide column store

Secondary database models

Graph DBMS
Search engine

Document store

Spatial DBMS

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

Score	0.20
Rank	#318	Overall
	#48	Key-value stores
	#141	Relational DBMS

Score	0.97
Rank	#192	Overall
	#32	Document stores
	#6	Object oriented DBMS

Score	29.04
Rank	#27	Overall
	#4	Document stores
	#2	Graph DBMS
	#3	Key-value stores
	#3	Wide column stores

Score	4.48
Rank	#75	Overall
	#6	Wide column stores

Website

www.faircom.com/products/faircom-db

www.gigaspaces.com

www.intersystems.com/products/cache

azure.microsoft.com/services/cosmos-db

azure.microsoft.com/en-us/services/storage/tables

Technical documentation

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

docs.gigaspaces.com/latest/landing.html

docs.intersystems.com

learn.microsoft.com/azure/cosmos-db

Developer

FairCom Corporation

Gigaspaces Technologies

InterSystems

Microsoft

Initial release

1979

2000

1997

2014

2012

Current release

V12, November 2020

15.5, September 2020

2018.1.4, May 2020

License

Commercial or Open Source

commercial

Restricted, free version available

Open Source

Apache Version 2; Commercial licenses available

commercial

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

ANSI C, C++

Java, C++, .Net

Server operating systems

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

easily portable to other OSs

Linux
macOS
Solaris
Windows

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

hosted

Data scheme

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

schema-free

depending on used data model

schema-free

Typing

predefined data types such as float or date

yes, ANSI SQL Types, JSON, typed binary structures

yes

JSON types

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.

XML can be used for describing objects metadata

yes

Secondary indexes

yes

All properties auto-indexed by default

SQL

Support of SQL

yes, ANSI SQL with proprietary extensions

SQL-99 for query and DML statements

yes

SQL-like query language

APIs and other access methods

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

GigaSpaces LRMI
Hibernate
JCache
JDBC
JPA
ODBC
RESTful HTTP API
Spring Data

.NET Client API
JDBC
ODBC
RESTful HTTP API

DocumentDB API
Graph API (Gremlin)
MongoDB API
RESTful HTTP API
Table API

RESTful HTTP API

Supported programming languages

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

.Net
C++
Java
Python
Scala

C#
C++
Java

.Net
C#
Java
JavaScript
JavaScript (Node.js)
MongoDB client drivers written for various programming languages
Python

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

Server-side scripts

Stored procedures

yes

.Net, JavaScript, C/C++

yes

JavaScript

Triggers

yes

yes, event driven architecture

yes

JavaScript

Partitioning methods

Methods for storing different data on different nodes

File partitioning, horizontal partitioning, sharding

Customizable business rules for table partitioning

Sharding

none

Sharding

Implicit feature of the cloud service

Sharding

Implicit feature of the cloud service

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).

Multi-source replication

synchronous or asynchronous
Source-replica replication

synchronous or asynchronous

Source-replica replication

yes

Implicit feature of the cloud service

yes

implicit feature of the cloud service. Replication either local, cross-facility or geo-redundant.

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Map-Reduce pattern can be built with XAP task executors

with Hadoop integration

Integration with Hadoop/HDInsight on Azure*

Consistency concepts

Methods to ensure consistency in a distributed system

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

Immediate Consistency

Consistency level configurable: ALL, QUORUM, ANY

Immediate Consistency

Bounded Staleness
Consistent Prefix
Eventual Consistency
Immediate Consistency

Consistency level configurable on request level
Session Consistency

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

tunable from ACID to Eventually Consistent

ACID

Multi-item ACID transactions with snapshot isolation within a partition

optimistic locking

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

Role-based access control

Access rights for users, groups and roles

Access rights can be defined down to the item level

Access rights based on private key authentication or shared access signatures

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.