DBMS > Blueflood vs. IBM Cloudant vs. Microsoft Azure Cosmos DB vs. TigerGraph vs. Yanza

System Properties Comparison Blueflood vs. IBM Cloudant vs. Microsoft Azure Cosmos DB vs. TigerGraph vs. Yanza

Editorial information provided by DB-Engines

Name

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

Description

Scalable TimeSeries DBMS based on Cassandra

Database as a Service offering based on Apache CouchDB

Globally distributed, horizontally scalable, multi-model database service

A complete, distributed, parallel graph computing platform supporting web-scale data analytics in real-time

Time Series DBMS for IoT Applications

Primary database model

Time Series DBMS

Document store

Document store
Graph DBMS
Key-value store
Wide column store

Graph DBMS

Time Series DBMS

Secondary database models

Spatial DBMS

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

Score	0.09
Rank	#353	Overall
	#33	Time Series DBMS

Score	2.73
Rank	#108	Overall
	#20	Document stores

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

Score	1.83
Rank	#141	Overall
	#13	Graph DBMS

Website

blueflood.io

www.ibm.com/products/cloudant

azure.microsoft.com/services/cosmos-db

www.tigergraph.com

yanza.com

Technical documentation

github.com/rax-maas/blueflood/wiki

cloud.ibm.com/docs/Cloudant

learn.microsoft.com/azure/cosmos-db

docs.tigergraph.com

Developer

Rackspace

IBM, Apache Software Foundation

IBM acquired Cloudant in February 2014

Microsoft

Yanza

Initial release

2013

2010

2014

2017

2015

License

Commercial or Open Source

Open Source

Apache 2.0

commercial

free version available

Cloud-based only

Only available as a cloud service

yes

but mainly used as a service provided by Yanza

DBaaS offerings (sponsored links)

Database as a Service

Providers of DBaaS offerings, please contact us to be listed.

Implementation language

Java

Erlang

C++

Server operating systems

Linux
OS X

hosted

Linux

Windows

Data scheme

predefined scheme

schema-free

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

SQL-like query language

SQL-like query language (GSQL)

APIs and other access methods

HTTP REST

RESTful HTTP/JSON API

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

GSQL (TigerGraph Query Language)
Kafka
RESTful HTTP/JSON API

HTTP API

Supported programming languages

C#
Java
JavaScript
Objective-C
PHP
Ruby

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

C++
Java

any language that supports HTTP calls

Server-side scripts

Stored procedures

View functions (Map-Reduce) in JavaScript

JavaScript

yes

Triggers

yes

JavaScript

yes

Timer and event based

Partitioning methods

Methods for storing different data on different nodes

Sharding

based on Cassandra

Sharding

Implicit feature of the cloud service

none

Replication methods

Methods for redundantly storing data on multiple nodes

selectable replication factor

based on Cassandra

Multi-source replication
Source-replica replication

yes

Implicit feature of the cloud service

none

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

with Hadoop integration

Integration with Hadoop/HDInsight on Azure*

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency

based on Cassandra
Immediate Consistency

based on Cassandra

Eventual Consistency

Bounded Staleness
Consistent Prefix
Eventual Consistency
Immediate Consistency

Consistency level configurable on request level
Session Consistency

Immediate Consistency

Foreign keys

Referential integrity

yes

Relationships in graphs

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

yes

In-memory capabilities

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

User concepts

Access control

Access rights for users can be defined per database

Access rights can be defined down to the item level

Role-based access control

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.