DBMS > AnzoGraph DB vs. IRONdb vs. Microsoft Azure Cosmos DB vs. Transwarp KunDB

System Properties Comparison AnzoGraph DB vs. IRONdb vs. Microsoft Azure Cosmos DB vs. Transwarp KunDB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

IRONdb seems to be discontinued. Therefore it is excluded from the DB-Engines Ranking.

Description

Scalable graph database built for online analytics and data harmonization with MPP scaling, high-performance analytical algorithms and reasoning, and virtualization

A distributed Time Series DBMS with a focus on scalability, fault tolerance and operational simplicity

Globally distributed, horizontally scalable, multi-model database service

OLTP DBMS based on a distributed architecture and highly compatible with MySQL and Oracle

Primary database model

Graph DBMS
RDF store

Time Series DBMS

Document store
Graph DBMS
Key-value store
Wide column store

Relational DBMS

Secondary database models

Spatial DBMS

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

Score	0.29
Rank	#303	Overall
	#25	Graph DBMS
	#14	RDF stores

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

Score	0.14
Rank	#341	Overall
	#149	Relational DBMS

Website

cambridgesemantics.com/anzograph

www.circonus.com/solutions/time-series-database/

azure.microsoft.com/services/cosmos-db

www.transwarp.cn/en/product/kundb

Technical documentation

docs.cambridgesemantics.com/anzograph/userdoc/home.htm

docs.circonus.com/irondb/category/getting-started

learn.microsoft.com/azure/cosmos-db

Developer

Cambridge Semantics

Circonus LLC.

Microsoft

Transwarp

Initial release

2018

2017

2014

Current release

2.3, January 2021

V0.10.20, January 2018

License

Commercial or Open Source

commercial

free trial version 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

C and C++

Server operating systems

Linux

hosted

Data scheme

Schema-free and OWL/RDFS-schema support

schema-free

yes

Typing

predefined data types such as float or date

yes

text, numeric, histograms

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

yes

SQL

Support of SQL

SPARQL and SPARQL* as primary query language. Cypher preview.

SQL-like query language (Circonus Analytics Query Language: CAQL)

SQL-like query language

yes

APIs and other access methods

Apache Mule
gRPC
JDBC
Kafka
OData access for BI tools
OpenCypher
RESTful HTTP API
SPARQL

HTTP API

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

Supported programming languages

C++
Java
Python

.Net
C
C++
Clojure
Erlang
Go
Haskell
Java
JavaScript
JavaScript (Node.js)
Lisp
Lua
Perl
PHP
Python
R
Ruby
Rust
Scala

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

Server-side scripts

Stored procedures

user defined functions and aggregates

yes, in Lua

JavaScript

yes

Triggers

JavaScript

yes

Partitioning methods

Methods for storing different data on different nodes

Automatic sharding

Automatic, metric affinity per node

Sharding

Implicit feature of the cloud service

horizontal partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication in MPP-Cluster

configurable replication factor, datacenter aware

yes

Implicit feature of the cloud service

MapReduce

Offers an API for user-defined Map/Reduce methods

Kerberos/HDFS data loading

with Hadoop integration

Integration with Hadoop/HDInsight on Azure*

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency in MPP-Cluster

Immediate consistency per node, eventual consistency across nodes

Bounded Staleness
Consistent Prefix
Eventual Consistency
Immediate Consistency

Consistency level configurable on request level
Session Consistency

Immediate Consistency

Foreign keys

Referential integrity

not needed in graphs

yes

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

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 and roles

Access rights can be defined down to the item level

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.