DBMS > BoltDB vs. Heroic vs. Memcached vs. MySQL vs. OpenQM

System Properties Comparison BoltDB vs. Heroic vs. Memcached vs. MySQL vs. OpenQM

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

In-memory key-value store, originally intended for caching

Widely used open source RDBMS

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

Primary database model

Key/Value like access via memcached API

Multivalue DBMS

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.51
Rank	#255	Overall
	#21	Time Series DBMS

Score	19.42
Rank	#32	Overall
	#4	Key-value stores

Score	1083.74
Rank	#2	Overall
	#2	Relational DBMS

Score	0.27
Rank	#298	Overall
	#10	Multivalue DBMS

Website

github.com/boltdb/bolt

github.com/spotify/heroic

www.memcached.org

www.mysql.com

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

Technical documentation

spotify.github.io/heroic

github.com/memcached/memcached/wiki

dev.mysql.com/doc

Developer

Spotify

Danga Interactive

originally developed by Brad Fitzpatrick for LiveJournal

Oracle

since 2010, originally MySQL AB, then Sun

Rocket Software, originally Martin Phillips

Initial release

2013

2014

2003

1995

1993

Current release

1.6.25, March 2024

8.3.0, January 2024

3.4-12

License

Commercial or Open Source

Open Source

MIT License

Open Source

Apache 2.0

Open Source

BSD license

Open Source

GPL version 2. Commercial licenses with extended functionallity are available

Open Source

GPLv2, extended 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 MySQL: Fully managed MySQL, deployable in the cloud of your choice, with seamless integrations and lightning-fast setup.

Implementation language

Java

C and C++

Server operating systems

BSD
Linux
OS X
Solaris
Windows

FreeBSD
Linux
OS X
Unix
Windows

FreeBSD
Linux
OS X
Solaris
Windows

AIX
FreeBSD
Linux
macOS
Raspberry Pi
Solaris
Windows

Data scheme

schema-free

yes

with some exceptions

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

Secondary indexes

yes

via Elasticsearch

yes

SQL

Support of SQL

yes

with proprietary extensions

APIs and other access methods

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

Proprietary protocol

ADO.NET
JDBC
ODBC
Proprietary native API

Supported programming languages

.Net
C
C++
ColdFusion
Erlang
Java
Lisp
Lua
OCaml
Perl
PHP
Python
Ruby

Ada
C
C#
C++
D
Delphi
Eiffel
Erlang
Haskell
Java
JavaScript (Node.js)
Objective-C
OCaml
Perl
PHP
Python
Ruby
Scheme
Tcl

.Net
Basic
C
Java
Objective C
PHP
Python

Server-side scripts

Stored procedures

yes

proprietary syntax

yes

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

none

horizontal partitioning, sharding with MySQL Cluster or MySQL Fabric

yes

Replication methods

Methods for redundantly storing data on multiple nodes

none

yes

none

Repcached, a Memcached patch, provides this functionallity

Multi-source replication
Source-replica replication

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

none

Eventual Consistency
Immediate Consistency

Immediate Consistency

Foreign keys

Referential integrity

yes

not for MyISAM storage engine

Transaction concepts

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

yes

ACID

not for MyISAM storage engine

ACID

Concurrency

Support for concurrent manipulation of data

yes

table locks or row locks depending on storage engine

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 SASL (Simple Authentication and Security Layer) protocol

Users with fine-grained authorization concept

no user groups or roles

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.