DBMS > BigchainDB vs. Elasticsearch vs. EXASOL vs. GeoMesa vs. SAP HANA

System Properties Comparison BigchainDB vs. Elasticsearch vs. EXASOL vs. GeoMesa vs. SAP HANA

Editorial information provided by DB-Engines

Name

Description

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

A distributed, RESTful modern search and analytics engine based on Apache Lucene

Elasticsearch lets you perform and combine many types of searches such as structured, unstructured, geo, and metric

High-performance, in-memory, MPP database specifically designed for in-memory analytics.

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
Spatial DBMS
Vector DBMS

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	135.35
Rank	#7	Overall
	#1	Search engines

Score	1.99
Rank	#124	Overall
	#58	Relational DBMS

Score	0.78
Rank	#213	Overall
	#4	Spatial DBMS

Score	44.69
Rank	#22	Overall
	#16	Relational DBMS

Website

www.bigchaindb.com

www.elastic.co/elasticsearch

www.exasol.com

www.geomesa.org

www.sap.com/products/hana.html

Technical documentation

bigchaindb.readthedocs.io/en/latest

www.elastic.co/guide/en/elasticsearch/reference/current/index.html

www.exasol.com/resources

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

help.sap.com/hana

Developer

Elastic

Exasol

CCRi and others

SAP

Initial release

2016

2010

2000

2014

2010

Current release

8.6, January 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

Elastic License

commercial

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

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

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

All search fields are automatically indexed

yes

SQL

Support of SQL

SQL-like query language

yes

APIs and other access methods

CLI Client
RESTful HTTP API

Java API
RESTful HTTP/JSON API

.Net
JDBC
ODBC
WebSocket

JDBC
ODBC

Supported programming languages

Go
Haskell
Java
JavaScript
Python
Ruby

.Net
Groovy
Community Contributed Clients
Java
JavaScript
Perl
PHP
Python
Ruby

Java
Lua
Python
R

Server-side scripts

Stored procedures

yes

user defined functions

SQLScript, R

Triggers

yes

by using the 'percolation' feature

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

depending on storage layer

yes

Replication methods

Methods for redundantly storing data on multiple nodes

selectable replication factor

yes

depending on storage layer

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

ES-Hadoop Connector

yes

Hadoop integration

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency

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

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.

Memcached and Redis integration

yes

depending on storage layer

yes

User concepts

Access control

yes

Access rights for users, groups and roles 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.