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

System Properties Comparison BigchainDB vs. GeoMesa vs. SAP HANA vs. WakandaDB

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

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

WakandaDB is embedded in a server that provides a REST API and a server-side javascript engine to access data

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	0.78
Rank	#213	Overall
	#4	Spatial DBMS

Score	44.69
Rank	#22	Overall
	#16	Relational DBMS

Score	0.03
Rank	#364	Overall
	#17	Object oriented DBMS

Website

www.bigchaindb.com

www.geomesa.org

www.sap.com/products/hana.html

wakanda.github.io

Technical documentation

bigchaindb.readthedocs.io/en/latest

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

help.sap.com/hana

wakanda.github.io/doc

Developer

CCRi and others

SAP

Wakanda SAS

Initial release

2016

2014

2010

2012

Current release

4.0.5, February 2024

2.0 SPS07 (April 4, 2023), April 2023

2.7.0 (April 29, 2019), April 2019

License

Commercial or Open Source

Open Source

AGPL v3

Open Source

Apache License 2.0

commercial

Open Source

AGPLv3, extended commercial license available

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

Scala

C++, JavaScript

Server operating systems

Linux

Appliance or cloud-service

Linux
OS X
Windows

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.

Secondary indexes

yes

SQL

Support of SQL

yes

APIs and other access methods

CLI Client
RESTful HTTP API

JDBC
ODBC

RESTful HTTP API

Supported programming languages

Go
Haskell
Java
JavaScript
Python
Ruby

JavaScript

Server-side scripts

Stored procedures

SQLScript, R

yes

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

depending on storage layer

yes

none

Replication methods

Methods for redundantly storing data on multiple nodes

selectable replication factor

depending on storage layer

yes

none

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

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.

depending on storage layer

yes

User concepts

Access control

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.