DBMS > BigchainDB vs. etcd vs. Quasardb vs. Snowflake vs. Solr

System Properties Comparison BigchainDB vs. etcd vs. Quasardb vs. Snowflake vs. Solr

Editorial information provided by DB-Engines

Name

Description

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

A distributed reliable key-value store

Distributed, high-performance timeseries database

Cloud-based data warehousing service for structured and semi-structured data

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

Primary database model

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	7.25
Rank	#54	Overall
	#5	Key-value stores

Score	0.14
Rank	#332	Overall
	#29	Time Series DBMS

Score	121.33
Rank	#9	Overall
	#6	Relational DBMS

Score	42.91
Rank	#24	Overall
	#3	Search engines

Website

www.bigchaindb.com

etcd.io
github.com/etcd-io/etcd

quasar.ai

www.snowflake.com

solr.apache.org

Technical documentation

bigchaindb.readthedocs.io/en/latest

etcd.io/docs
github.com/etcd-io/etcd/tree/master/Documentation

doc.quasar.ai/master

docs.snowflake.net/manuals/index.html

solr.apache.org/resources.html

Developer

quasardb

Snowflake Computing Inc.

Apache Software Foundation

Initial release

2016

2009

2014

2006

Current release

3.4, August 2019

3.14.1, January 2024

9.6.0, April 2024

License

Commercial or Open Source

Open Source

AGPL v3

Open Source

Apache Version 2.0

commercial

Free community edition, Non-profit organizations and non-commercial usage are eligible for free licenses

commercial

Open Source

Apache Version 2

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

Java

Server operating systems

Linux

FreeBSD
Linux
Windows

experimental

BSD
Linux
OS X
Windows

hosted

All OS with a Java VM

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

Data scheme

schema-free

yes

support of semi-structured data formats (JSON, XML, Avro)

yes

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

Typing

predefined data types such as float or date

yes

integer and binary

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

with tags

yes

All search fields are automatically indexed

SQL

Support of SQL

SQL-like query language

yes

Solr Parallel SQL Interface

APIs and other access methods

CLI Client
RESTful HTTP API

gRPC
JSON over HTTP

HTTP API

CLI Client
JDBC
ODBC

Java API
RESTful HTTP/JSON API

Supported programming languages

Go
Haskell
Java
JavaScript
Python
Ruby

.Net
C
C++
Clojure
Erlang
Go
Haskell
Java
JavaScript (Node.js)
Perl
PHP
Python
R
Ruby
Rust
Scala
Tcl

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

JavaScript (Node.js)
Python

.Net
Erlang
Java
JavaScript
any language that supports sockets and either XML or JSON
Perl
PHP
Python
Ruby
Scala

Server-side scripts

Stored procedures

user defined functions

Java plugins

Triggers

yes, watching key changes

similar concept for controling cloud resources

yes

User configurable commands triggered on index changes

Partitioning methods

Methods for storing different data on different nodes

Sharding

consistent hashing

yes

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

selectable replication factor

Using Raft consensus algorithm to ensure data replication with strong consistency among multiple replicas.

Source-replica replication with selectable replication factor

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

with Hadoop integration

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

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

optimistic locking

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes,with MongoDB ord RethinkDB

yes

by using LevelDB

yes

In-memory capabilities

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

yes

Transient mode

yes

User concepts

Access control

yes

Cryptographically strong user authentication and audit trail

Users with fine-grained authorization concept, user roles and pluggable authentication

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.