DBMS > BoltDB vs. Heroic vs. MaxDB vs. OpenSearch vs. RavenDB

System Properties Comparison BoltDB vs. Heroic vs. MaxDB vs. OpenSearch vs. RavenDB

Editorial information provided by DB-Engines

Name

Description

An embedded key-value store for Go.

Time Series DBMS built at Spotify based on Cassandra or Google Cloud Bigtable, and ElasticSearch

A robust and reliable RDBMS optimized to run all major SAP solutions

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

Open Source Operational and Transactional Enterprise NoSQL Document Database

Primary database model

Secondary database models

Vector DBMS

Graph DBMS
Spatial DBMS
Time Series DBMS

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

Score	0.74
Rank	#220	Overall
	#31	Key-value stores

Score	0.51
Rank	#255	Overall
	#21	Time Series DBMS

Score	2.32
Rank	#112	Overall
	#55	Relational DBMS

Score	16.36
Rank	#37	Overall
	#4	Search engines

Score	2.92
Rank	#101	Overall
	#18	Document stores

Website

github.com/boltdb/bolt

github.com/spotify/heroic

maxdb.sap.com

github.com/opensearch-project
opensearch.org

ravendb.net

Technical documentation

spotify.github.io/heroic

maxdb.sap.com/documentation

opensearch.org/docs/latest

ravendb.net/docs

Developer

Spotify

SAP, acquired from Software AG (Adabas-D) in 1997

Amazon Web Services

Hibernating Rhinos

Initial release

2013

2014

1984

2021

2010

Current release

7.9.10.12, February 2024

2.5.0, January 2023

5.4, July 2022

License

Commercial or Open Source

Open Source

MIT License

Open Source

Apache 2.0

commercial

Limited community edition free

Open Source

Apache Version 2.0

Open Source

AGPL version 3, commercial license available

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

Java

C++

Java

Server operating systems

BSD
Linux
OS X
Solaris
Windows

AIX
HP-UX
Linux
Solaris
Windows

All OS with a Java VM

Linux
macOS
Raspberry Pi
Windows

Data scheme

schema-free

yes

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

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

via Elasticsearch

yes

All search fields are automatically indexed

yes

SQL

Support of SQL

yes

SQL-like query language

SQL-like query language (RQL)

APIs and other access methods

HQL (Heroic Query Language, a JSON-based language)
HTTP API

ADO.NET
JDBC
ODBC
WebDAV

Java API
RESTful HTTP/JSON API

.NET Client API
F# Client API
Go Client API
Java Client API
NodeJS Client API
PHP Client API
Python Client API
RESTful HTTP API

Supported programming languages

.Net
C#
Java
Perl
PHP
Python

Go
Java
JavaScript (Node.js)
PHP
Python
Ruby

Elasticsearch client

.Net
C#
F#
Go
Java
JavaScript (Node.js)
PHP
Python
Ruby

Server-side scripts

Stored procedures

yes

Triggers

yes

by using the 'percolation' feature

yes

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

none

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

none

yes

Source-replica replication

yes

Multi-source replication

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

none

Eventual Consistency
Immediate Consistency

Immediate Consistency

Eventual Consistency

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

Default ACID transactions on the local node (eventually consistent across the cluster). Atomic operations with cluster-wide ACID transactions. Eventual consistency for indexes and full-text search indexes.

Foreign keys

Referential integrity

yes

Transaction concepts

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

yes

ACID

ACID, Cluster-wide transaction available

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

In-memory capabilities

Is there an option to define some or all structures to be held in-memory only.

User concepts

Access control

fine grained access rights according to SQL-standard

Authorization levels configured per client per database

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.