DBMS > Graph Engine vs. IBM Cloudant vs. Microsoft Azure Cosmos DB vs. VelocityDB

System Properties Comparison Graph Engine vs. IBM Cloudant vs. Microsoft Azure Cosmos DB vs. VelocityDB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

A distributed in-memory data processing engine, underpinned by a strongly-typed RAM store and a general distributed computation engine

Database as a Service offering based on Apache CouchDB

Globally distributed, horizontally scalable, multi-model database service

A .NET Object Database that can be embedded/distributed and extended to a graph data model (VelocityGraph)

Primary database model

Graph DBMS
Key-value store

Document store

Document store
Graph DBMS
Key-value store
Wide column store

Graph DBMS
Object oriented DBMS

Secondary database models

Spatial DBMS

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

Score	0.56
Rank	#241	Overall
	#21	Graph DBMS
	#34	Key-value stores

Score	2.85
Rank	#95	Overall
	#18	Document stores

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

Score	0.00
Rank	#385	Overall
	#40	Graph DBMS
	#21	Object oriented DBMS

Website

www.graphengine.io

www.ibm.com/products/cloudant

azure.microsoft.com/services/cosmos-db

velocitydb.com

Technical documentation

www.graphengine.io/docs/manual

cloud.ibm.com/docs/Cloudant

learn.microsoft.com/azure/cosmos-db

velocitydb.com/UserGuide

Developer

Microsoft

IBM, Apache Software Foundation

IBM acquired Cloudant in February 2014

Microsoft

VelocityDB Inc

Initial release

2010

2014

2011

Current release

7.x

License

Commercial or Open Source

Open Source

MIT License

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

.NET and C

Erlang

Server operating systems

.NET

hosted

Any that supports .NET

Data scheme

yes

schema-free

yes

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

yes

SQL

Support of SQL

SQL-like query language

APIs and other access methods

RESTful HTTP API

RESTful HTTP/JSON API

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

.Net

Supported programming languages

C#
C++
F#
Visual Basic

C#
Java
JavaScript
Objective-C
PHP
Ruby

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

.Net

Server-side scripts

Stored procedures

yes

View functions (Map-Reduce) in JavaScript

JavaScript

Triggers

yes

JavaScript

Callbacks are triggered when data changes

Partitioning methods

Methods for storing different data on different nodes

horizontal partitioning

Sharding

Implicit feature of the cloud service

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication
Source-replica replication

yes

Implicit feature of the cloud service

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

with Hadoop integration

Integration with Hadoop/HDInsight on Azure*

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency

Bounded Staleness
Consistent Prefix
Eventual Consistency
Immediate Consistency

Consistency level configurable on request level
Session Consistency

Immediate Consistency

Foreign keys

Referential integrity

Transaction concepts

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

atomic operations within a document possible

Multi-item ACID transactions with snapshot isolation within a partition

ACID

Concurrency

Support for concurrent manipulation of data

yes

Optimistic locking

yes

Durability

Support for making data persistent

optional: either by committing a write-ahead log (WAL) to the local persistent storage or by dumping the memory to a persistent storage

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 can be defined per database

Access rights can be defined down to the item level

Based on Windows Authentication

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.