DBMS > BigchainDB vs. Microsoft Azure Cosmos DB vs. Solr vs. SWC-DB

System Properties Comparison BigchainDB vs. Microsoft Azure Cosmos DB vs. Solr vs. SWC-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

Globally distributed, horizontally scalable, multi-model database service

A widely used distributed, scalable search engine based on Apache Lucene

A high performance, scalable Wide Column DBMS

Primary database model

Document store

Document store
Graph DBMS
Key-value store
Wide column store

Search engine

Wide column store

Secondary database models

Spatial DBMS

Time Series DBMS

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

Score	0.79
Rank	#212	Overall
	#36	Document stores

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

Score	42.91
Rank	#24	Overall
	#3	Search engines

Score	0.01
Rank	#376	Overall
	#13	Wide column stores

Website

www.bigchaindb.com

azure.microsoft.com/services/cosmos-db

solr.apache.org

github.com/kashirin-alex/swc-db
www.swcdb.org

Technical documentation

bigchaindb.readthedocs.io/en/latest

learn.microsoft.com/azure/cosmos-db

solr.apache.org/resources.html

Developer

Microsoft

Apache Software Foundation

Alex Kashirin

Initial release

2016

2014

2006

2020

Current release

9.5.0, February 2024

0.5, April 2021

License

Commercial or Open Source

Open Source

AGPL v3

commercial

Open Source

Apache Version 2

Open Source

GPL V3

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

Server operating systems

Linux

hosted

All OS with a Java VM

runs as a servlet in servlet container (e.g. Tomcat, Jetty is included)

Linux

Data scheme

schema-free

yes

Dynamic Fields enables on-the-fly addition of new fields

schema-free

Typing

predefined data types such as float or date

yes

JSON types

yes

supports customizable data types and automatic typing

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

All search fields are automatically indexed

SQL

Support of SQL

SQL-like query language

Solr Parallel SQL Interface

SQL-like query language

APIs and other access methods

CLI Client
RESTful HTTP API

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

Java API
RESTful HTTP/JSON API

Proprietary protocol
Thrift

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
Erlang
Java
JavaScript
any language that supports sockets and either XML or JSON
Perl
PHP
Python
Ruby
Scala

C++

Server-side scripts

Stored procedures

JavaScript

Java plugins

Triggers

JavaScript

yes

User configurable commands triggered on index changes

Partitioning methods

Methods for storing different data on different nodes

Sharding

Implicit feature of the cloud service

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

selectable replication factor

yes

Implicit feature of the cloud service

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

with Hadoop integration

Integration with Hadoop/HDInsight on Azure*

spark-solr: github.com/lucidworks/spark-solr and streaming expressions to reduce

Consistency concepts

Methods to ensure consistency in a distributed system

Bounded Staleness
Consistent Prefix
Eventual Consistency
Immediate Consistency

Consistency level configurable on request level
Session Consistency

Eventual 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 can be defined down to the item level

yes

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.