DBMS > BigchainDB vs. Blazegraph vs. Heroic vs. Microsoft Azure Cosmos DB vs. Transbase

System Properties Comparison BigchainDB vs. Blazegraph vs. Heroic vs. Microsoft Azure Cosmos DB vs. Transbase

Editorial information provided by DB-Engines

Name

Amazon has acquired Blazegraph's domain and (probably) product. It is said that Amazon Neptune is based on Blazegraph.

Description

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

High-performance graph database supporting Semantic Web (RDF/SPARQL) and Graph Database (tinkerpop3, blueprints, vertex-centric) APIs with scale-out and High Availability.

Time Series DBMS built at Spotify based on Cassandra or Google Cloud Bigtable, and ElasticSearch

Globally distributed, horizontally scalable, multi-model database service

A resource-optimized, high-performance, universally applicable RDBMS

Primary database model

Document store

Graph DBMS
RDF 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.79
Rank	#212	Overall
	#36	Document stores

Score	0.75
Rank	#219	Overall
	#19	Graph DBMS
	#8	RDF stores

Score	0.51
Rank	#255	Overall
	#21	Time Series DBMS

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

Score	0.11
Rank	#341	Overall
	#150	Relational DBMS

Website

www.bigchaindb.com

blazegraph.com

github.com/spotify/heroic

azure.microsoft.com/services/cosmos-db

www.transaction.de/en/products/transbase.html

Technical documentation

bigchaindb.readthedocs.io/en/latest

wiki.blazegraph.com

spotify.github.io/heroic

learn.microsoft.com/azure/cosmos-db

www.transaction.de/en/products/transbase/features.html

Developer

Blazegraph

Spotify

Microsoft

Transaction Software GmbH

Initial release

2016

2006

2014

1987

Current release

2.1.5, March 2019

Transbase 8.3, 2022

License

Commercial or Open Source

Open Source

AGPL v3

Open Source

extended commercial license available

Open Source

Apache 2.0

commercial

free development license

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

Java

C and C++

Server operating systems

Linux

Linux
OS X
Windows

hosted

FreeBSD
Linux
macOS
Solaris
Windows

Data scheme

schema-free

yes

Typing

predefined data types such as float or date

yes

RDF literal types

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

via Elasticsearch

yes

All properties auto-indexed by default

yes

SQL

Support of SQL

SPARQL is used as query language

SQL-like query language

yes

APIs and other access methods

CLI Client
RESTful HTTP API

Java API
RESTful HTTP API
SPARQL QUERY
SPARQL UPDATE
TinkerPop 3

HQL (Heroic Query Language, a JSON-based language)
HTTP API

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

ADO.NET
JDBC
ODBC
Proprietary native API

Supported programming languages

Go
Haskell
Java
JavaScript
Python
Ruby

.Net
C
C++
Java
JavaScript
PHP
Python
Ruby

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

C
C#
C++
Java
JavaScript
Kotlin
Objective-C
PHP
Python

Server-side scripts

Stored procedures

yes

JavaScript

yes

Triggers

JavaScript

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

Implicit feature of the cloud service

Replication methods

Methods for redundantly storing data on multiple nodes

selectable replication factor

yes

Implicit feature of the cloud service

Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

with Hadoop integration

Integration with Hadoop/HDInsight on Azure*

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency or Eventual Consistency depending on configuration

Eventual Consistency
Immediate 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

yes

Transaction concepts

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

ACID

Multi-item ACID transactions with snapshot isolation within a partition

yes

Concurrency

Support for concurrent manipulation of data

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

Security and Authentication via Web Application Container (Tomcat, Jetty)

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.