DBMS > BoltDB vs. DolphinDB vs. Heroic vs. RavenDB vs. SwayDB

System Properties Comparison BoltDB vs. DolphinDB vs. Heroic vs. RavenDB vs. SwayDB

Editorial information provided by DB-Engines

Name

Description

DolphinDB is a high performance Time Series DBMS. It is integrated with an easy-to-use fully featured programming language and a high-volume high-velocity streaming analytics system. It offers operational simplicity, scalability, fault tolerance, and concurrency.

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

Open Source Operational and Transactional Enterprise NoSQL Document Database

An embeddable, non-blocking, type-safe key-value store for single or multiple disks and in-memory storage

Primary database model

Secondary database models

Relational DBMS

Graph DBMS
Spatial DBMS
Time Series DBMS

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

Score	0.74
Rank	#220	Overall
	#31	Key-value stores

Score	4.13
Rank	#80	Overall
	#6	Time Series DBMS

Score	0.51
Rank	#255	Overall
	#21	Time Series DBMS

Score	2.92
Rank	#101	Overall
	#18	Document stores

Score	0.00
Rank	#382	Overall
	#59	Key-value stores

Website

github.com/boltdb/bolt

www.dolphindb.com

github.com/spotify/heroic

ravendb.net

swaydb.simer.au

Technical documentation

docs.dolphindb.cn/en/help200/index.html

spotify.github.io/heroic

ravendb.net/docs

Developer

DolphinDB, Inc

Spotify

Hibernating Rhinos

Simer Plaha

Initial release

2013

2018

2014

2010

2018

Current release

v2.00.4, January 2022

5.4, July 2022

License

Commercial or Open Source

Open Source

MIT License

commercial

free community version available

Open Source

Apache 2.0

Open Source

AGPL version 3, commercial license available

Open Source

GNU Affero GPL V3.0

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

C++

Java

Scala

Server operating systems

BSD
Linux
OS X
Solaris
Windows

Linux
Windows

Linux
macOS
Raspberry Pi
Windows

Data scheme

schema-free

yes

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

yes

SQL

Support of SQL

SQL-like query language

SQL-like query language (RQL)

APIs and other access methods

JDBC
JSON over HTTP
Kafka
MQTT (Message Queue Telemetry Transport)
ODBC
OPC DA
OPC UA
RabbitMQ
WebSocket

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

.NET Client API
F# Client API
Go Client API
Java Client API
NodeJS Client API
PHP Client API
Python Client API
RESTful HTTP API

Supported programming languages

C#
C++
Go
Java
JavaScript
MatLab
Python
R
Rust

.Net
C#
F#
Go
Java
JavaScript (Node.js)
PHP
Python
Ruby

Java
Kotlin
Scala

Server-side scripts

Stored procedures

yes

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

none

horizontal partitioning

Sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

none

yes

Multi-source replication

none

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

none

Immediate Consistency

Eventual Consistency
Immediate Consistency

Default ACID transactions on the local node (eventually consistent across the cluster). Atomic operations with cluster-wide ACID transactions. Eventual consistency for indexes and full-text search indexes.

Immediate Consistency

Foreign keys

Referential integrity

Transaction concepts

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

yes

ACID, Cluster-wide transaction available

Atomic execution of operations

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

Administrators, Users, Groups

Authorization levels configured per client per database

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.

Related products and services

We invite representatives of vendors of related products to contact us for presenting information about their offerings here.

More resources

Recent citations in the news

What I learnt from building 3 high traffic web applications on an embedded key value store.
21 February 2018, hackernoon.com

4 Instructive Postmortems on Data Downtime and Loss
1 March 2024, The Hacker News

Three Reasons DevOps Should Consider Rocky Linux 9.4
15 May 2024, DevOps.com

Roblox’s cloud-native catastrophe: A post mortem
31 January 2022, InfoWorld

How to Put a GUI on Ansible, Using Semaphore
22 April 2023, The New Stack

provided by Google News

RavenDB Welcomes David Baruc as Chief Revenue Officer: Seasoned Tech Leader to Drive Global Sales and ...
13 June 2023, PR Newswire

Install the NoSQL RavenDB Data System
14 May 2021, The New Stack

Oren Eini on RavenDB, Including Consistency Guarantees and C# as the Implementation Language
23 May 2022, InfoQ.com

RavenDB Adds Graph Queries
15 May 2019, Datanami

How I Created a RavenDB Python Client
23 September 2016, Visual Studio Magazine

provided by Google News

Share this page