DBMS > BoltDB vs. Heroic vs. OrigoDB vs. RocksDB vs. Solr

System Properties Comparison BoltDB vs. Heroic vs. OrigoDB vs. RocksDB vs. Solr

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 fully ACID in-memory object graph database

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

A widely used distributed, scalable search engine based on Apache Lucene

Primary database model

Key-value store

Time Series DBMS

Document store
Object oriented DBMS

Key-value store

Search engine

Secondary database models

Spatial DBMS

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

Score	0.76
Rank	#224	Overall
	#32	Key-value stores

Score	0.57
Rank	#250	Overall
	#21	Time Series DBMS

Score	0.03
Rank	#378	Overall
	#51	Document stores
	#18	Object oriented DBMS

Score	4.00
Rank	#84	Overall
	#11	Key-value stores

Score	44.28
Rank	#24	Overall
	#3	Search engines

Website

github.com/boltdb/bolt

github.com/spotify/heroic

origodb.com

rocksdb.org

solr.apache.org

Technical documentation

spotify.github.io/heroic

origodb.com/docs

github.com/facebook/rocksdb/wiki

solr.apache.org/resources.html

Developer

Spotify

Robert Friberg et al

Facebook, Inc.

Apache Software Foundation

Initial release

2013

2014

2009

under the name LiveDB

2013

2006

Current release

8.11.4, April 2024

9.5.0, February 2024

License

Commercial or Open Source

Open Source

MIT License

Open Source

Apache 2.0

Open Source

BSD

Open Source

Apache Version 2

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

Java

C++

Java

Server operating systems

BSD
Linux
OS X
Solaris
Windows

Linux
Windows

Linux

All OS with a Java VM

runs as a servlet in servlet container (e.g. Tomcat, Jetty is included)

Data scheme

schema-free

yes

schema-free

yes

Dynamic Fields enables on-the-fly addition of new fields

Typing

predefined data types such as float or date

yes

User defined using .NET types and collections

yes

supports customizable data types and automatic typing

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.

can be achieved using .NET

yes

Secondary indexes

yes

via Elasticsearch

yes

All search fields are automatically indexed

SQL

Support of SQL

Solr Parallel SQL Interface

APIs and other access methods

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

.NET Client API
HTTP API
LINQ

C++ API
Java API

Java API
RESTful HTTP/JSON API

Supported programming languages

.Net

C
C++
Go
Java
Perl
Python
Ruby

.Net
Erlang
Java
JavaScript
any language that supports sockets and either XML or JSON
Perl
PHP
Python
Ruby
Scala

Server-side scripts

Stored procedures

yes

Java plugins

Triggers

yes

Domain Events

yes

User configurable commands triggered on index changes

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

horizontal partitioning

client side managed; servers are not synchronized

horizontal partitioning

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

none

yes

Source-replica replication

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

spark-solr: github.com/lucidworks/spark-solr and streaming expressions to reduce

Consistency concepts

Methods to ensure consistency in a distributed system

none

Eventual Consistency
Immediate Consistency

Eventual Consistency

Foreign keys

Referential integrity

depending on model

Transaction concepts

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

yes

ACID

yes

optimistic locking

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

Write ahead log

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

Role based authorization

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.