DBMS > BigchainDB vs. HarperDB vs. OrigoDB vs. SAP HANA

System Properties Comparison BigchainDB vs. HarperDB vs. OrigoDB vs. SAP HANA

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

Ultra-low latency distributed database with an intuitive REST API supporting NoSQL and SQL (including joins). Deployment of functions and databases simultaneously with a consolidated node-level architecture.

A fully ACID in-memory object graph database

In-memory, column based data store. Available as appliance or cloud service

Primary database model

Document store

Document store
Object oriented DBMS

Relational DBMS

Secondary database models

Document store
Graph DBMS

with SAP Hana, Enterprise Edition
Spatial DBMS

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

Score	0.85
Rank	#208	Overall
	#35	Document stores

Score	0.60
Rank	#244	Overall
	#38	Document stores

Score	0.06
Rank	#380	Overall
	#50	Document stores
	#18	Object oriented DBMS

Score	44.27
Rank	#23	Overall
	#16	Relational DBMS

Website

www.bigchaindb.com

www.harperdb.io

origodb.com

www.sap.com/products/hana.html

Technical documentation

bigchaindb.readthedocs.io/en/latest

docs.harperdb.io/docs

origodb.com/docs

help.sap.com/hana

Developer

HarperDB

Robert Friberg et al

SAP

Initial release

2016

2017

2009

under the name LiveDB

2010

Current release

3.1, August 2021

2.0 SPS07 (April 4, 2023), April 2023

License

Commercial or Open Source

Open Source

AGPL v3

commercial

free community edition available

Open Source

commercial

Cloud-based only

Only available as a cloud service

also available as a cloud based service

DBaaS offerings (sponsored links)

Database as a Service

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

Implementation language

Python

Node.js

Server operating systems

Linux

Linux
OS X

Linux
Windows

Appliance or cloud-service

Data scheme

schema-free

dynamic schema

yes

Typing

predefined data types such as float or date

yes

JSON data types

User defined using .NET types and collections

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.

can be achieved using .NET

Secondary indexes

yes

SQL

Support of SQL

SQL-like data manipulation statements

yes

APIs and other access methods

CLI Client
RESTful HTTP API

JDBC
ODBC
React Hooks
RESTful HTTP/JSON API
WebSocket

.NET Client API
HTTP API
LINQ

JDBC
ODBC

Supported programming languages

Go
Haskell
Java
JavaScript
Python
Ruby

.Net
C
C#
C++
ColdFusion
D
Dart
Delphi
Erlang
Go
Haskell
Java
JavaScript (Node.js)
Lisp
MatLab
Objective C
Perl
PHP
PowerShell
Prolog
Python
R
Ruby
Rust
Scala
Swift

.Net

Server-side scripts

Stored procedures

Custom Functions

since release 3.1

yes

SQLScript, R

Triggers

yes

Domain Events

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

A table resides as a whole on one (or more) nodes in a cluster

horizontal partitioning

client side managed; servers are not synchronized

yes

Replication methods

Methods for redundantly storing data on multiple nodes

selectable replication factor

yes

the nodes on which a table resides can be defined

Source-replica replication

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Foreign keys

Referential integrity

depending on model

yes

Transaction concepts

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

Atomic execution of specific operations

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes,with MongoDB ord RethinkDB

yes, using LMDB

yes

Write ahead log

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

Role based authorization

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.