DBMS > BigchainDB vs. Cubrid vs. GeoMesa vs. Microsoft Azure Cosmos DB

System Properties Comparison BigchainDB vs. Cubrid vs. GeoMesa vs. Microsoft Azure Cosmos DB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

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

CUBRID is an open-source SQL-based relational database management system with object extensions for OLTP

GeoMesa is a distributed spatio-temporal DBMS based on various systems as storage layer.

Globally distributed, horizontally scalable, multi-model database service

Primary database model

Document store

Relational DBMS

Spatial DBMS

Document store
Graph DBMS
Key-value store
Wide column store

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	1.20
Rank	#169	Overall
	#78	Relational DBMS

Score	0.78
Rank	#213	Overall
	#4	Spatial DBMS

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

Website

www.bigchaindb.com

cubrid.com (korean)
cubrid.org (english)

www.geomesa.org

azure.microsoft.com/services/cosmos-db

Technical documentation

bigchaindb.readthedocs.io/en/latest

cubrid.org/manuals

www.geomesa.org/documentation/stable/user/index.html

learn.microsoft.com/azure/cosmos-db

Developer

CUBRID Corporation, CUBRID Foundation

CCRi and others

Microsoft

Initial release

2016

2008

2014

Current release

11.0, January 2021

4.0.5, February 2024

License

Commercial or Open Source

Open Source

AGPL v3

Open Source

Apache Version 2.0

Open Source

Apache License 2.0

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

Python

C, C++, Java

Scala

Server operating systems

Linux

Linux
Windows

hosted

Data scheme

schema-free

yes

schema-free

Typing

predefined data types such as float or date

yes

JSON types

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

yes

SQL-like query language

APIs and other access methods

CLI Client
RESTful HTTP API

ADO.NET
JDBC
ODBC
OLE DB

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

Supported programming languages

Go
Haskell
Java
JavaScript
Python
Ruby

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

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

Server-side scripts

Stored procedures

Java Stored Procedures

JavaScript

Triggers

yes

JavaScript

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

depending on storage layer

Sharding

Implicit feature of the cloud service

Replication methods

Methods for redundantly storing data on multiple nodes

selectable replication factor

Source-replica replication

depending on storage layer

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

Immediate Consistency

depending on storage layer

Bounded Staleness
Consistent Prefix
Eventual Consistency
Immediate Consistency

Consistency level configurable on request level
Session Consistency

Foreign keys

Referential integrity

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

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.

depending on storage layer

User concepts

Access control

yes

fine grained access rights according to SQL-standard

yes

depending on the DBMS used for storage

Access rights can be defined down to the item level

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.