DBMS > BigchainDB vs. Graphite vs. Microsoft Azure Cosmos DB vs. Trafodion

System Properties Comparison BigchainDB vs. Graphite vs. Microsoft Azure Cosmos DB vs. Trafodion

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Apache Trafodion has been retired in 2021. Therefore it is excluded from the DB-Engines Ranking.

Description

BigchainDB is scalable blockchain database offering decentralization, immutability and native assets

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

Transactional SQL-on-Hadoop DBMS

Primary database model

Document 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.85
Rank	#208	Overall
	#35	Document stores

Score	4.83
Rank	#67	Overall
	#4	Time Series DBMS

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

Website

www.bigchaindb.com

github.com/graphite-project/graphite-web

azure.microsoft.com/services/cosmos-db

trafodion.apache.org

Technical documentation

bigchaindb.readthedocs.io/en/latest

graphite.readthedocs.io

learn.microsoft.com/azure/cosmos-db

trafodion.apache.org/documentation.html

Developer

Chris Davis

Microsoft

Apache Software Foundation, originally developed by HP

Initial release

2016

2006

2014

Current release

2.3.0, February 2019

License

Commercial or Open Source

Open Source

AGPL v3

Open Source

Apache 2.0

commercial

Open Source

Apache 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

Python

C++, Java

Server operating systems

Linux

Linux
Unix

hosted

Linux

Data scheme

schema-free

yes

schema-free

yes

Typing

predefined data types such as float or date

Numeric data only

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

yes

APIs and other access methods

CLI Client
RESTful HTTP API

HTTP API
Sockets

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

ADO.NET
JDBC
ODBC

Supported programming languages

Go
Haskell
Java
JavaScript
Python
Ruby

JavaScript (Node.js)
Python

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

All languages supporting JDBC/ODBC/ADO.Net

Server-side scripts

Stored procedures

JavaScript

Java Stored Procedures

Triggers

JavaScript

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

Sharding

Implicit feature of the cloud service

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

selectable replication factor

none

yes

Implicit feature of the cloud service

yes, via HBase

MapReduce

Offers an API for user-defined Map/Reduce methods

with Hadoop integration

Integration with Hadoop/HDInsight on Azure*

yes

via user defined functions and HBase

Consistency concepts

Methods to ensure consistency in a distributed system

none

Bounded Staleness
Consistent Prefix
Eventual Consistency
Immediate Consistency

Consistency level configurable on request level
Session Consistency

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

Multi-item ACID transactions with snapshot isolation within a partition

ACID

Concurrency

Support for concurrent manipulation of data

yes

locking

yes

Durability

Support for making data persistent

yes,with MongoDB ord RethinkDB

yes

In-memory capabilities

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

User concepts

Access control

yes

Access rights can be defined down to the item level

fine grained access rights according to SQL-standard

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.