DBMS > BigchainDB vs. GeoSpock vs. Microsoft Azure Cosmos DB vs. Microsoft Azure Table Storage vs. YottaDB

System Properties Comparison BigchainDB vs. GeoSpock vs. Microsoft Azure Cosmos DB vs. Microsoft Azure Table Storage vs. YottaDB

Editorial information provided by DB-Engines

Name

GeoSpock seems to be discontinued. Therefore it will be excluded from the DB-Engines ranking.

Description

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

Spatial and temporal data processing engine for extreme data scale

Globally distributed, horizontally scalable, multi-model database service

A Wide Column Store for rapid development using massive semi-structured datasets

A fast and solid embedded Key-value store

Primary database model

Document store

Relational DBMS

Document store
Graph DBMS
Key-value store
Wide column store

Wide column store

Key-value store

Secondary database models

Time Series DBMS

Spatial DBMS

Relational DBMS

using the Octo plugin

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

Score	0.85
Rank	#208	Overall
	#35	Document stores

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

Score	4.04
Rank	#77	Overall
	#6	Wide column stores

Score	0.28
Rank	#306	Overall
	#44	Key-value stores

Website

www.bigchaindb.com

geospock.com

azure.microsoft.com/services/cosmos-db

azure.microsoft.com/en-us/services/storage/tables

yottadb.com

Technical documentation

bigchaindb.readthedocs.io/en/latest

learn.microsoft.com/azure/cosmos-db

yottadb.com/resources/documentation

Developer

GeoSpock

Microsoft

YottaDB, LLC

Initial release

2016

2014

2012

2001

Current release

2.0, September 2019

License

Commercial or Open Source

Open Source

AGPL v3

commercial

Open Source

AGPL 3.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

Java, Javascript

Server operating systems

Linux

hosted

Docker
Linux

Data 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

temporal, categorical

yes

All properties auto-indexed by default

SQL

Support of SQL

ANSI SQL for query only (using Presto)

SQL-like query language

by using the Octo plugin

APIs and other access methods

CLI Client
RESTful HTTP API

JDBC

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

RESTful HTTP API

PostgreSQL wire protocol

using the Octo plugin
Proprietary protocol

Supported programming languages

Go
Haskell
Java
JavaScript
Python
Ruby

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

.Net
C#
C++
Java
JavaScript (Node.js)
PHP
Python
Ruby

C
Go
JavaScript (Node.js)
Lua
M
Perl
Python
Rust

Server-side scripts

Stored procedures

JavaScript

Triggers

JavaScript

Partitioning methods

Methods for storing different data on different nodes

Sharding

Automatic sharding

Sharding

Implicit feature of the cloud service

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

yes

implicit feature of the cloud service. Replication either local, cross-facility or geo-redundant.

yes

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

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

Multi-item ACID transactions with snapshot isolation within a partition

optimistic locking

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.

yes

User concepts

Access control

yes

Access rights for users can be defined per table

Access rights can be defined down to the item level

Access rights based on private key authentication or shared access signatures

Users and groups based on OS-security mechanisms

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.