DBMS > BigchainDB vs. Hive vs. Netezza vs. RocksDB vs. Solr

System Properties Comparison BigchainDB vs. Hive vs. Netezza vs. RocksDB vs. Solr

Editorial information provided by DB-Engines

Name

Description

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

data warehouse software for querying and managing large distributed datasets, built on Hadoop

Data warehouse and analytics appliance part of IBM PureSystems

Embeddable persistent key-value store optimized for fast storage (flash and RAM)

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	61.17
Rank	#18	Overall
	#12	Relational DBMS

Score	9.06
Rank	#46	Overall
	#29	Relational DBMS

Score	3.65
Rank	#85	Overall
	#11	Key-value stores

Score	42.91
Rank	#24	Overall
	#3	Search engines

Website

www.bigchaindb.com

hive.apache.org

www.ibm.com/products/netezza

rocksdb.org

solr.apache.org

Technical documentation

bigchaindb.readthedocs.io/en/latest

cwiki.apache.org/confluence/display/Hive/Home

github.com/facebook/rocksdb/wiki

solr.apache.org/resources.html

Developer

Apache Software Foundation

initially developed by Facebook

IBM

Facebook, Inc.

Apache Software Foundation

Initial release

2016

2012

2000

2013

2006

Current release

3.1.3, April 2022

9.2.1, May 2024

9.6.0, April 2024

License

Commercial or Open Source

Open Source

AGPL v3

Open Source

Apache Version 2

commercial

Open Source

BSD

Open Source

Apache Version 2

Cloud-based only

Only available as a cloud service

DBaaS offerings (sponsored links)

Database as a Service

Providers of DBaaS offerings, please contact us to be listed.

Implementation language

Python

Java

C++

Java

Server operating systems

Linux

All OS with a Java VM

Linux

included in appliance

Linux

All OS with a Java VM

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

Data scheme

schema-free

yes

schema-free

yes

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

Typing

predefined data types such as float or date

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 search fields are automatically indexed

SQL

Support of SQL

SQL-like DML and DDL statements

yes

Solr Parallel SQL Interface

APIs and other access methods

CLI Client
RESTful HTTP API

JDBC
ODBC
Thrift

JDBC
ODBC
OLE DB

C++ API
Java API

Java API
RESTful HTTP/JSON API

Supported programming languages

Go
Haskell
Java
JavaScript
Python
Ruby

C++
Java
PHP
Python

C
C++
Fortran
Java
Lua
Perl
Python
R

C
C++
Go
Java
Perl
Python
Ruby

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

Server-side scripts

Stored procedures

yes

user defined functions and integration of map-reduce

yes

Java plugins

Triggers

yes

User configurable commands triggered on index changes

Partitioning methods

Methods for storing different data on different nodes

Sharding

horizontal partitioning

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

selectable replication factor

Source-replica replication

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

query execution via MapReduce

yes

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

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency

Foreign keys

Referential integrity

Transaction concepts

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

ACID

yes

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, groups and roles

Users with fine-grained authorization concept

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.