DBMS > InterSystems Caché vs. Microsoft Azure Cosmos DB vs. TigerGraph vs. TinkerGraph

System Properties Comparison InterSystems Caché vs. Microsoft Azure Cosmos DB vs. TigerGraph vs. TinkerGraph

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

A multi-model DBMS and application server

Globally distributed, horizontally scalable, multi-model database service

A complete, distributed, parallel graph computing platform supporting web-scale data analytics in real-time

A lightweight, in-memory graph engine that serves as a reference implementation of the TinkerPop3 API

Primary database model

Key-value store
Object oriented DBMS
Relational DBMS

Document store
Graph DBMS
Key-value store
Wide column store

Graph DBMS

Secondary database models

Document store

Spatial DBMS

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

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

Score	1.44
Rank	#152	Overall
	#14	Graph DBMS

Score	0.08
Rank	#345	Overall
	#34	Graph DBMS

Website

www.intersystems.com/products/cache

azure.microsoft.com/services/cosmos-db

www.tigergraph.com

tinkerpop.apache.org/docs/current/reference/#tinkergraph-gremlin

Technical documentation

docs.intersystems.com

learn.microsoft.com/azure/cosmos-db

docs.tigergraph.com

Developer

InterSystems

Microsoft

Initial release

1997

2014

2017

2009

Current release

2018.1.4, May 2020

License

Commercial or Open Source

commercial

Open Source

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

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

hosted

Linux

Data scheme

depending on used data model

schema-free

yes

schema-free

Typing

predefined data types such as float or date

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.

yes

Secondary indexes

yes

All properties auto-indexed by default

SQL

Support of SQL

yes

SQL-like query language

SQL-like query language (GSQL)

APIs and other access methods

.NET Client API
JDBC
ODBC
RESTful HTTP API

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

GSQL (TigerGraph Query Language)
Kafka
RESTful HTTP/JSON API

TinkerPop 3

Supported programming languages

C#
C++
Java

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

C++
Java

Groovy
Java

Server-side scripts

Stored procedures

yes

JavaScript

yes

Triggers

yes

JavaScript

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

Implicit feature of the cloud service

none

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

yes

Implicit feature of the cloud service

none

MapReduce

Offers an API for user-defined Map/Reduce methods

with Hadoop integration

Integration with Hadoop/HDInsight on Azure*

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Bounded Staleness
Consistent Prefix
Eventual Consistency
Immediate Consistency

Consistency level configurable on request level
Session Consistency

none

Foreign keys

Referential integrity

yes

Relationships in graphs

yes

Relationships in graphs

Transaction concepts

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

ACID

Multi-item ACID transactions with snapshot isolation within a partition

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

optional

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

Access rights can be defined down to the item level

Role-based access control

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.