DBMS > Heroic vs. RocksDB vs. SWC-DB vs. TerminusDB vs. WakandaDB

System Properties Comparison Heroic vs. RocksDB vs. SWC-DB vs. TerminusDB vs. WakandaDB

Editorial information provided by DB-Engines

Name

Description

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)

A high performance, scalable Wide Column DBMS

Scalable Graph Database platform making enterprise data available by exploiting inferred entities and relationships

WakandaDB is embedded in a server that provides a REST API and a server-side javascript engine to access data

Primary database model

Secondary database models

Time Series DBMS

Document store
RDF store

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

Score	0.51
Rank	#255	Overall
	#21	Time Series DBMS

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

Score	0.01
Rank	#376	Overall
	#13	Wide column stores

Score	0.17
Rank	#325	Overall
	#29	Graph DBMS

Score	0.03
Rank	#364	Overall
	#17	Object oriented DBMS

Website

github.com/spotify/heroic

rocksdb.org

github.com/kashirin-alex/swc-db
www.swcdb.org

terminusdb.com

wakanda.github.io

Technical documentation

spotify.github.io/heroic

github.com/facebook/rocksdb/wiki

terminusdb.github.io/terminusdb/#

wakanda.github.io/doc

Developer

Spotify

Facebook, Inc.

Alex Kashirin

DataChemist Ltd.

Wakanda SAS

Initial release

2014

2013

2020

2018

2012

Current release

8.11.4, April 2024

0.5, April 2021

11.0.0, January 2023

2.7.0 (April 29, 2019), April 2019

License

Commercial or Open Source

Open Source

Apache 2.0

Open Source

BSD

Open Source

GPL V3

Open Source

GPL V3

Open Source

AGPLv3, 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.

Implementation language

Java

C++

Prolog, Rust

C++, JavaScript

Server operating systems

Linux

Linux
OS X
Windows

Data scheme

schema-free

yes

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

SQL-like query language

SQL-like query language (WOQL)

APIs and other access methods

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

C++ API
Java API

Proprietary protocol
Thrift

OWL
RESTful HTTP API
WOQL (Web Object Query Language)

RESTful HTTP API

Supported programming languages

C
C++
Go
Java
Perl
Python
Ruby

C++

JavaScript
Python

JavaScript

Server-side scripts

Stored procedures

yes

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

horizontal partitioning

Sharding

Graph Partitioning

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Journaling Streams

none

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

yes

Transaction concepts

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

yes

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

in-memory journaling

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 access control

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.