DBMS > BoltDB vs. HarperDB vs. Heroic vs. Postgres-XL vs. RocksDB

System Properties Comparison BoltDB vs. HarperDB vs. Heroic vs. Postgres-XL vs. RocksDB

Editorial information provided by DB-Engines

Name

Description

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.

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

Based on PostgreSQL enhanced with MPP and write-scale-out cluster features

Embeddable persistent key-value store optimized for fast storage (flash and RAM)

Primary database model

Secondary database models

Document store
Spatial 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.55
Rank	#248	Overall
	#38	Document stores

Score	0.51
Rank	#255	Overall
	#21	Time Series DBMS

Score	0.49
Rank	#256	Overall
	#117	Relational DBMS

Score	3.65
Rank	#85	Overall
	#11	Key-value stores

Website

github.com/boltdb/bolt

www.harperdb.io

github.com/spotify/heroic

www.postgres-xl.org

rocksdb.org

Technical documentation

docs.harperdb.io/docs

spotify.github.io/heroic

www.postgres-xl.org/documentation

github.com/facebook/rocksdb/wiki

Developer

HarperDB

Spotify

Facebook, Inc.

Initial release

2013

2017

2014

since 2012, originally named StormDB

2013

Current release

3.1, August 2021

10 R1, October 2018

9.2.1, May 2024

License

Commercial or Open Source

Open Source

MIT License

commercial

free community edition available

Open Source

Apache 2.0

Open Source

Mozilla public license

Open Source

BSD

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.

Implementation language

Node.js

Java

C++

Server operating systems

BSD
Linux
OS X
Solaris
Windows

Linux
OS X

Linux
macOS

Linux

Data scheme

schema-free

dynamic schema

schema-free

yes

schema-free

Typing

predefined data types such as float or date

yes

JSON data types

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

XML type, but no XML query functionality

Secondary indexes

yes

via Elasticsearch

yes

SQL

Support of SQL

SQL-like data manipulation statements

yes

distributed, parallel query execution

APIs and other access methods

JDBC
ODBC
React Hooks
RESTful HTTP/JSON API
WebSocket

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

ADO.NET
JDBC
native C library
ODBC
streaming API for large objects

C++ API
Java API

Supported programming languages

.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
C
C++
Delphi
Erlang
Java
JavaScript (Node.js)
Perl
PHP
Python
Tcl

C
C++
Go
Java
Perl
Python
Ruby

Server-side scripts

Stored procedures

Custom Functions

since release 3.1

user defined functions

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

none

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

Sharding

horizontal partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

none

yes

the nodes on which a table resides can be defined

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

none

Immediate Consistency

Eventual Consistency
Immediate Consistency

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

yes

Atomic execution of specific operations

ACID

MVCC

yes

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

yes, using LMDB

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

Access rights for users and roles

fine grained access rights according to SQL-standard

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.