DBMS > BigchainDB vs. Derby vs. GeoMesa vs. SAP HANA

System Properties Comparison BigchainDB vs. Derby vs. GeoMesa 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

Full-featured RDBMS with a small footprint, either embedded into a Java application or used as a database server.

GeoMesa is a distributed spatio-temporal DBMS based on various systems as storage layer.

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

Primary database model

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.79
Rank	#212	Overall
	#36	Document stores

Score	4.71
Rank	#69	Overall
	#37	Relational DBMS

Score	0.78
Rank	#213	Overall
	#4	Spatial DBMS

Score	44.69
Rank	#22	Overall
	#16	Relational DBMS

Website

www.bigchaindb.com

db.apache.org/derby

www.geomesa.org

www.sap.com/products/hana.html

Technical documentation

bigchaindb.readthedocs.io/en/latest

db.apache.org/derby/manuals/index.html

www.geomesa.org/documentation/stable/user/index.html

help.sap.com/hana

Developer

Apache Software Foundation

CCRi and others

SAP

Initial release

2016

1997

2014

2010

Current release

10.17.1.0, November 2023

4.0.5, February 2024

2.0 SPS07 (April 4, 2023), April 2023

License

Commercial or Open Source

Open Source

AGPL v3

Open Source

Apache version 2

Open Source

Apache License 2.0

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

Java

Scala

Server operating systems

Linux

All OS with a Java VM

Appliance or cloud-service

Data scheme

schema-free

yes

Typing

predefined data types such as float or date

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.

yes

Secondary indexes

yes

SQL

Support of SQL

yes

APIs and other access methods

CLI Client
RESTful HTTP API

JDBC

JDBC
ODBC

Supported programming languages

Go
Haskell
Java
JavaScript
Python
Ruby

Java

Server-side scripts

Stored procedures

Java Stored Procedures

SQLScript, R

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

depending on storage layer

yes

Replication methods

Methods for redundantly storing data on multiple nodes

selectable replication factor

Source-replica replication

depending on storage layer

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

depending on storage layer

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

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

depending on storage layer

yes

User concepts

Access control

yes

fine grained access rights according to SQL-standard

yes

depending on the DBMS used for storage

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.