DBMS > AgensGraph vs. IBM Db2 vs. Microsoft Azure Cosmos DB vs. TinkerGraph

System Properties Comparison AgensGraph vs. IBM Db2 vs. Microsoft Azure Cosmos DB vs. TinkerGraph

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Multi-model database supporting relational and graph data models and built upon PostgreSQL

Common in IBM host environments, 2 different versions for host and Windows/Linux

Globally distributed, horizontally scalable, multi-model database service

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

Primary database model

Graph DBMS
Relational DBMS

Relational DBMS

Since Version 10.5 support for JSON/BSON documents compatible with MongoDB

Document store
Graph DBMS
Key-value store
Wide column store

Graph DBMS

Secondary database models

Document store
RDF store

in Db2 LUW (Linux, Unix, Windows)
Spatial DBMS

with Db2 Spatial Extender

Spatial DBMS

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

Score	0.20
Rank	#321	Overall
	#27	Graph DBMS
	#143	Relational DBMS

Score	128.46
Rank	#8	Overall
	#5	Relational DBMS

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

Score	0.08
Rank	#348	Overall
	#35	Graph DBMS

Website

bitnine.net/agensgraph

www.ibm.com/products/db2

azure.microsoft.com/services/cosmos-db

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

Technical documentation

bitnine.net/documentation

www.ibm.com/docs/en/db2

learn.microsoft.com/azure/cosmos-db

Developer

Bitnine Global Inc.

IBM

Microsoft

Initial release

2016

1983

host version

2014

2009

Current release

2.1, December 2018

12.1, October 2016

License

Commercial or Open Source

Open Source

Apache License 2.0

commercial

free version is available

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

Java

Server operating systems

Linux
OS X
Windows

AIX
HP-UX
Linux
Solaris
Windows
z/OS

hosted

Data scheme

depending on used data model

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.

Secondary indexes

yes

All properties auto-indexed by default

SQL

Support of SQL

yes

SQL-like query language

APIs and other access methods

Cypher Query Language
JDBC

ADO.NET
JDBC
JSON style queries

MongoDB compatible
ODBC
XQuery

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

TinkerPop 3

Supported programming languages

C
Java
JavaScript
Python

C
C#
C++
Cobol
Delphi
Fortran
Java
Perl
PHP
Python
Ruby
Visual Basic

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

Groovy
Java

Server-side scripts

Stored procedures

yes

JavaScript

Triggers

yes

JavaScript

Partitioning methods

Methods for storing different data on different nodes

no, but can be realized using table inheritance

Sharding

only with Windows/Unix/Linux Version

Sharding

Implicit feature of the cloud service

none

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

yes

with separate tools (MQ, InfoSphere)

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*

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

Transaction concepts

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

ACID

Multi-item ACID transactions with snapshot isolation within a partition

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

fine grained access rights according to SQL-standard

Access rights can be defined down to the item level

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.