DBMS > BigchainDB vs. Datomic vs. Microsoft Azure Cosmos DB vs. Microsoft Azure Table Storage vs. searchxml

System Properties Comparison BigchainDB vs. Datomic vs. Microsoft Azure Cosmos DB vs. Microsoft Azure Table Storage vs. searchxml

Editorial information provided by DB-Engines

Name

Description

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

Datomic builds on immutable values, supports point-in-time queries and uses 3rd party systems for durability

Globally distributed, horizontally scalable, multi-model database service

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

DBMS for structured and unstructured content wrapped with an application server

Primary database model

Document store

Relational DBMS

Document store
Graph DBMS
Key-value store
Wide column store

Wide column store

Native XML DBMS
Search engine

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.59
Rank	#150	Overall
	#69	Relational DBMS

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

Score	4.48
Rank	#75	Overall
	#6	Wide column stores

Score	0.00
Rank	#383	Overall
	#7	Native XML DBMS
	#25	Search engines

Website

www.bigchaindb.com

www.datomic.com

azure.microsoft.com/services/cosmos-db

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

www.searchxml.net/category/products

Technical documentation

bigchaindb.readthedocs.io/en/latest

docs.datomic.com

learn.microsoft.com/azure/cosmos-db

www.searchxml.net/support/handouts

Developer

Cognitect

Microsoft

informationpartners gmbh

Initial release

2016

2012

2014

2012

2015

Current release

1.0.6735, June 2023

1.0

License

Commercial or Open Source

Open Source

AGPL v3

commercial

limited edition free

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

Java, Clojure

C++

Server operating systems

Linux

All OS with a Java VM

hosted

Windows

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.

yes

Secondary indexes

yes

All properties auto-indexed by default

yes

SQL

Support of SQL

SQL-like query language

APIs and other access methods

CLI Client
RESTful HTTP API

RESTful HTTP API

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

RESTful HTTP API

RESTful HTTP API
WebDAV
XQuery
XSLT

Supported programming languages

Go
Haskell
Java
JavaScript
Python
Ruby

Clojure
Java

.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++

most other programming languages supported via APIs

Server-side scripts

Stored procedures

yes

Transaction Functions

JavaScript

yes

on the application server

Triggers

By using transaction functions

JavaScript

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

But extensive use of caching in the application peers

Sharding

Implicit feature of the cloud service

Sharding

Implicit feature of the cloud service

none

Replication methods

Methods for redundantly storing data on multiple nodes

selectable replication factor

none

But extensive use of caching in the application peers

yes

Implicit feature of the cloud service

yes

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

yes

sychronisation to multiple collections

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

ACID

Multi-item ACID transactions with snapshot isolation within a partition

optimistic locking

multiple readers, single writer

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes,with MongoDB ord RethinkDB

yes

using external storage systems (e.g. Cassandra, DynamoDB, PostgreSQL, Couchbase and others)

yes

In-memory capabilities

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

yes

recommended only for testing and development

User concepts

Access control

yes

Access rights can be defined down to the item level

Access rights based on private key authentication or shared access signatures

Domain, group and role-based access control at the document level and for application services

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.