DBMS > BoltDB vs. Heroic vs. RocksDB vs. Warp 10 vs. Yanza

System Properties Comparison BoltDB vs. Heroic vs. RocksDB vs. Warp 10 vs. Yanza

Editorial information provided by DB-Engines

Name

Yanza seems to be discontinued. Therefore it is excluded from the DB-Engines Ranking.

Description

An embedded key-value store for Go.

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

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

TimeSeries DBMS specialized on timestamped geo data based on LevelDB or HBase

Time Series DBMS for IoT Applications

Primary database model

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	3.65
Rank	#85	Overall
	#11	Key-value stores

Score	0.07
Rank	#349	Overall
	#32	Time Series DBMS

Website

github.com/boltdb/bolt

github.com/spotify/heroic

rocksdb.org

www.warp10.io

yanza.com

Technical documentation

spotify.github.io/heroic

github.com/facebook/rocksdb/wiki

www.warp10.io/content/02_Getting_started

Developer

Spotify

Facebook, Inc.

SenX

Yanza

Initial release

2013

2014

2013

2015

Current release

8.11.4, April 2024

License

Commercial or Open Source

Open Source

MIT License

Open Source

Apache 2.0

Open Source

BSD

Open Source

Apache License 2.0

commercial

free version available

Cloud-based only

Only available as a cloud service

but mainly used as a service provided by Yanza

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

Linux
OS X
Windows

Windows

Data scheme

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

SQL

Support of SQL

APIs and other access methods

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

C++ API
Java API

HTTP API
Jupyter
WebSocket

HTTP API

Supported programming languages

C
C++
Go
Java
Perl
Python
Ruby

any language that supports HTTP calls

Server-side scripts

Stored procedures

yes

WarpScript

Triggers

yes

Timer and event based

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

horizontal partitioning

Sharding

based on HBase

none

Replication methods

Methods for redundantly storing data on multiple nodes

none

yes

selectable replication factor

based on HBase

none

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

based on HBase

Immediate Consistency

Foreign keys

Referential integrity

Transaction concepts

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

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

Mandatory use of cryptographic tokens, containing fine-grained authorizations

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.