DBMS > AnzoGraph DB vs. Graphite vs. Microsoft Azure Cosmos DB vs. TerarkDB

System Properties Comparison AnzoGraph DB vs. Graphite vs. Microsoft Azure Cosmos DB vs. TerarkDB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

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

Data logging and graphing tool for time series data

The storage layer (fixed size database) is called Whisper

Globally distributed, horizontally scalable, multi-model database service

A key-value store forked from RocksDB with advanced compression algorithms. It can be used standalone or as a storage engine for MySQL and MongoDB

Primary database model

Graph DBMS
RDF store

Time Series DBMS

Document store
Graph DBMS
Key-value store
Wide column store

Key-value store

Secondary database models

Spatial DBMS

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

Score	0.27
Rank	#302	Overall
	#24	Graph DBMS
	#13	RDF stores

Score	4.75
Rank	#75	Overall
	#5	Time Series DBMS

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

Score	0.04
Rank	#377	Overall
	#58	Key-value stores

Website

cambridgesemantics.com/anzograph

github.com/graphite-project/graphite-web

azure.microsoft.com/services/cosmos-db

github.com/bytedance/terarkdb

Technical documentation

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

graphite.readthedocs.io

learn.microsoft.com/azure/cosmos-db

bytedance.larkoffice.com/docs/doccnZmYFqHBm06BbvYgjsHHcKc

Developer

Cambridge Semantics

Chris Davis

Microsoft

ByteDance, originally Terark

Initial release

2018

2006

2014

2016

Current release

2.3, January 2021

License

Commercial or Open Source

commercial

free trial version available

Open Source

Apache 2.0

commercial

restricted open source version available

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

Python

C++

Server operating systems

Linux

Linux
Unix

hosted

Data scheme

Schema-free and OWL/RDFS-schema support

yes

schema-free

Typing

predefined data types such as float or date

Numeric data only

yes

JSON types

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

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

SQL-like query language

APIs and other access methods

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

HTTP API
Sockets

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

C++ API
Java API

Supported programming languages

C++
Java
Python

JavaScript (Node.js)
Python

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

C++
Java

Server-side scripts

Stored procedures

user defined functions and aggregates

JavaScript

Triggers

JavaScript

Partitioning methods

Methods for storing different data on different nodes

Automatic sharding

none

Sharding

Implicit feature of the cloud service

none

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication in MPP-Cluster

none

yes

Implicit feature of the cloud service

none

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

none

Bounded Staleness
Consistent Prefix
Eventual Consistency
Immediate Consistency

Consistency level configurable on request level
Session Consistency

Foreign keys

Referential integrity

not needed 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

locking

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

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.