DBMS > AnzoGraph DB vs. LevelDB vs. Microsoft Azure Cosmos DB vs. Tkrzw

System Properties Comparison AnzoGraph DB vs. LevelDB vs. Microsoft Azure Cosmos DB vs. Tkrzw

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

Embeddable fast key-value storage library that provides an ordered mapping from string keys to string values

Globally distributed, horizontally scalable, multi-model database service

A concept of libraries, allowing an application program to store and query key-value pairs in a file. Successor of Tokyo Cabinet and Kyoto Cabinet

Primary database model

Graph DBMS
RDF store

Key-value store

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	2.75
Rank	#107	Overall
	#19	Key-value stores

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

Score	0.09
Rank	#354	Overall
	#51	Key-value stores

Website

cambridgesemantics.com/anzograph

github.com/google/leveldb

azure.microsoft.com/services/cosmos-db

dbmx.net/tkrzw

Technical documentation

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

github.com/google/leveldb/blob/main/doc/index.md

learn.microsoft.com/azure/cosmos-db

Developer

Cambridge Semantics

Google

Microsoft

Mikio Hirabayashi

Initial release

2018

2011

2014

2020

Current release

2.3, January 2021

1.23, February 2021

0.9.3, August 2020

License

Commercial or Open Source

commercial

free trial version available

Open Source

BSD

commercial

Open Source

Apache Version 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++

Server operating systems

Linux

Illumos
Linux
OS X
Windows

hosted

Linux
macOS

Data scheme

Schema-free and OWL/RDFS-schema support

schema-free

Typing

predefined data types such as float or date

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

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

Supported programming languages

C++
Java
Python

C++
Go
Java

3rd party binding
JavaScript (Node.js)

3rd party binding
Python

3rd party binding

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

C++
Java
Python
Ruby

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

Immediate Consistency

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

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

with automatic compression on writes

yes

In-memory capabilities

Is there an option to define some or all structures to be held in-memory only.

yes

using specific database classes

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.