DBMS > BigchainDB vs. EJDB vs. HBase vs. OpenSearch vs. PouchDB

System Properties Comparison BigchainDB vs. EJDB vs. HBase vs. OpenSearch vs. PouchDB

Editorial information provided by DB-Engines

Name

Description

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

Embeddable document-store database library with JSON representation of queries (in MongoDB style)

Wide-column store based on Apache Hadoop and on concepts of BigTable

A distributed, RESTful search and analytics engine forked from Elasticsearch and based on Apache Lucene

JavaScript DBMS with an API inspired by CouchDB

Primary database model

Secondary database models

Vector DBMS

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

Score	0.79
Rank	#212	Overall
	#36	Document stores

Score	0.27
Rank	#297	Overall
	#44	Document stores

Score	30.50
Rank	#26	Overall
	#2	Wide column stores

Score	16.36
Rank	#37	Overall
	#4	Search engines

Score	2.28
Rank	#115	Overall
	#21	Document stores

Website

www.bigchaindb.com

github.com/Softmotions/ejdb

hbase.apache.org

github.com/opensearch-project
opensearch.org

pouchdb.com

Technical documentation

bigchaindb.readthedocs.io/en/latest

github.com/Softmotions/ejdb/blob/master/README.md

hbase.apache.org/book.html

opensearch.org/docs/latest

pouchdb.com/guides

Developer

Softmotions

Apache Software Foundation

Apache top-level project, originally developed by Powerset

Amazon Web Services

Apache Software Foundation

Initial release

2016

2012

2008

2021

2012

Current release

2.3.4, January 2021

2.5.0, January 2023

7.1.1, June 2019

License

Commercial or Open Source

Open Source

AGPL v3

Open Source

GPLv2

Open Source

Apache version 2

Open Source

Apache Version 2.0

Open Source

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.

Aiven for OpenSearch: Fully managed open source search and analytics suite. Out-of-the-box integrations get you up and running in a couple of clicks.

Implementation language

Python

Java

JavaScript

Server operating systems

Linux

server-less

Linux
Unix
Windows

using Cygwin

All OS with a Java VM

server-less, requires a JavaScript environment (browser, Node.js)

Data scheme

schema-free

schema-free, schema definition possible

schema-free

Flexible type definitions. Once a type is defined, it is persistent

schema-free

Typing

predefined data types such as float or date

yes

string, integer, double, bool, date, object_id

options to bring your own types, AVRO

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.

Secondary indexes

yes

All search fields are automatically indexed

yes

via views

SQL

Support of SQL

SQL-like query language

APIs and other access methods

CLI Client
RESTful HTTP API

in-process shared library

Java API
RESTful HTTP API
Thrift

Java API
RESTful HTTP/JSON API

HTTP REST

only for PouchDB Server
JavaScript API

Supported programming languages

Go
Haskell
Java
JavaScript
Python
Ruby

Actionscript
C
C#
C++
Go
Java
JavaScript (Node.js)
Lua
Objective-C
Pike
Python
Ruby

C
C#
C++
Groovy
Java
PHP
Python
Scala

Go
Java
JavaScript (Node.js)
PHP
Python
Ruby

Elasticsearch client

JavaScript

Server-side scripts

Stored procedures

yes

Coprocessors in Java

yes

View functions in JavaScript

Triggers

yes

by using the 'percolation' feature

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

Sharding

with a proxy-based framework, named couchdb-lounge

Replication methods

Methods for redundantly storing data on multiple nodes

selectable replication factor

none

Multi-source replication
Source-replica replication

yes

Multi-source replication

also with CouchDB databases
Source-replica replication

also with CouchDB databases

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency or Eventual Consistency

Eventual Consistency

Synchronous doc based replication. Get by ID may show delays up to 1 sec. Configurable write consistency: one, quorum, all

Eventual Consistency

Foreign keys

Referential integrity

typically not needed, however similar functionality with collection joins possible

Transaction concepts

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

Single row ACID (across millions of columns)

Concurrency

Support for concurrent manipulation of data

yes

Read/Write Locking

yes

Durability

Support for making data persistent

yes,with MongoDB ord RethinkDB

yes

by using IndexedDB, WebSQL or LevelDB as backend

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 Control Lists (ACL) for RBAC, integration with Apache Ranger for RBAC & ABAC

More information provided by the system vendor

Specific characteristics

OpenSearch is a highly scalable and extensible open-source software suite for search,...
» more

Competitive advantages

Distributed as fully open source under Apache License, Version 2.0 (ALv2), OpenSearch...
» more

Typical application scenarios

The OpenSearch platform is used across a broad range of search , analytics, and observability...
» more

Licensing and pricing models

The OpenSearch Project offers open source software licensed under Apache License...
» more

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.