DBMS > Heroic vs. Microsoft Azure AI Search vs. OpenQM vs. Oracle Berkeley DB vs. RocksDB

System Properties Comparison Heroic vs. Microsoft Azure AI Search vs. OpenQM vs. Oracle Berkeley DB vs. RocksDB

Editorial information provided by DB-Engines

Name

Description

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

Search-as-a-service for web and mobile app development

QpenQM is a high-performance, self-tuning, multi-value DBMS

Widely used in-process key-value store

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

Primary database model

supports sorted and unsorted key sets
Native XML DBMS

in the Oracle Berkeley DB XML version

Key-value store

Secondary database models

Vector DBMS

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

Score	0.51
Rank	#255	Overall
	#21	Time Series DBMS

Score	5.59
Rank	#63	Overall
	#7	Search engines

Score	0.27
Rank	#298	Overall
	#10	Multivalue DBMS

Score	2.21
Rank	#117	Overall
	#20	Key-value stores
	#3	Native XML DBMS

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

Website

github.com/spotify/heroic

azure.microsoft.com/en-us/services/search

www.rocketsoftware.com/products/rocket-multivalue-application-development-platform/rocket-open-qm

www.oracle.com/database/technologies/related/berkeleydb.html

rocksdb.org

Technical documentation

spotify.github.io/heroic

learn.microsoft.com/en-us/azure/search

docs.oracle.com/cd/E17076_05/html/index.html

github.com/facebook/rocksdb/wiki

Developer

Spotify

Microsoft

Rocket Software, originally Martin Phillips

Oracle

originally developed by Sleepycat, which was acquired by Oracle

Facebook, Inc.

Initial release

2014

2015

1993

1994

2013

Current release

3.4-12

18.1.40, May 2020

9.2.1, May 2024

License

Commercial or Open Source

Open Source

Apache 2.0

commercial

Open Source

GPLv2, extended commercial license available

Open Source

commercial license available

Open Source

BSD

Cloud-based only

Only available as a cloud service

yes

DBaaS offerings (sponsored links)

Database as a Service

Providers of DBaaS offerings, please contact us to be listed.

Implementation language

Java

C, Java, C++ (depending on the Berkeley DB edition)

C++

Server operating systems

hosted

AIX
FreeBSD
Linux
macOS
Raspberry Pi
Solaris
Windows

AIX
Android
FreeBSD
iOS
Linux
OS X
Solaris
VxWorks
Windows

Linux

Data scheme

schema-free

yes

with some exceptions

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.

yes

only with the Berkeley DB XML edition

Secondary indexes

yes

via Elasticsearch

yes

SQL

Support of SQL

yes

SQL interfaced based on SQLite is available

APIs and other access methods

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

RESTful HTTP API

C++ API
Java API

Supported programming languages

C#
Java
JavaScript
Python

.Net
Basic
C
Java
Objective C
PHP
Python

.Net

Figaro is a .Net framework assembly that extends Berkeley DB XML into an embeddable database engine for .NET
others

Third-party libraries to manipulate Berkeley DB files are available for many languages
C
C#
C++
Java
JavaScript (Node.js)

3rd party binding
Perl
Python
Tcl

C
C++
Go
Java
Perl
Python
Ruby

Server-side scripts

Stored procedures

yes

Triggers

yes

only for the SQL API

Partitioning methods

Methods for storing different data on different nodes

Sharding

Implicit feature of the cloud service

yes

none

horizontal partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Implicit feature of the cloud service

yes

Source-replica replication

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency
Immediate Consistency

Immediate Consistency

Foreign keys

Referential integrity

Transaction concepts

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

ACID

yes

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.

yes

User concepts

Access control

yes

using Azure authentication

Access rights can be defined down to the item level

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.