DBMS > BoltDB vs. FatDB vs. Heroic vs. Transbase vs. VoltDB

System Properties Comparison BoltDB vs. FatDB vs. Heroic vs. Transbase vs. VoltDB

Editorial information provided by DB-Engines

Name

FatDB/FatCloud has ceased operations as a company with February 2014. FatDB is discontinued and excluded from the ranking.

Description

An embedded key-value store for Go.

A .NET NoSQL DBMS that can integrate with and extend SQL Server.

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

A resource-optimized, high-performance, universally applicable RDBMS

Distributed In-Memory NewSQL RDBMS

Used for OLTP applications with a high frequency of relatively simple transactions, that can hold all their data in memory

Primary database model

Key-value store

Document store
Key-value store

Time Series DBMS

Relational 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	0.11
Rank	#341	Overall
	#150	Relational DBMS

Score	1.44
Rank	#158	Overall
	#73	Relational DBMS

Website

github.com/boltdb/bolt

github.com/spotify/heroic

www.transaction.de/en/products/transbase.html

www.voltdb.com

Technical documentation

spotify.github.io/heroic

www.transaction.de/en/products/transbase/features.html

docs.voltdb.com

Developer

FatCloud

Spotify

Transaction Software GmbH

VoltDB Inc.

Initial release

2013

2012

2014

1987

2010

Current release

Transbase 8.3, 2022

11.3, April 2022

License

Commercial or Open Source

Open Source

MIT License

commercial

Open Source

Apache 2.0

commercial

free development license

Open Source

AGPL for Community Edition, commercial license for Enterprise, AWS, and Pro Editions

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 and C++

Java, C++

Server operating systems

BSD
Linux
OS X
Solaris
Windows

Windows

FreeBSD
Linux
macOS
Solaris
Windows

Linux
OS X

for development

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

yes

SQL

Support of SQL

Via inetgration in SQL Server

yes

only a subset of SQL 99

APIs and other access methods

.NET Client API
LINQ
RESTful HTTP API
RPC
Windows WCF Bindings

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

ADO.NET
JDBC
ODBC
Proprietary native API

Java API
JDBC
RESTful HTTP/JSON API

Supported programming languages

C
C#
C++
Java
JavaScript
Kotlin
Objective-C
PHP
Python

C#
C++
Erlang

not officially supported
Go
Java
JavaScript

Node.js
PHP
Python

Server-side scripts

Stored procedures

yes

via applications

yes

Java

Triggers

yes

via applications

yes

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

none

selectable replication factor

yes

Source-replica replication

Multi-source replication
Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

none

Eventual Consistency
Immediate Consistency

Immediate Consistency

Foreign keys

Referential integrity

yes

FOREIGN KEY constraints are not supported

Transaction concepts

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

yes

ACID

Transactions are executed single-threaded within stored procedures

Concurrency

Support for concurrent manipulation of data

yes

Data access is serialized by the server

Durability

Support for making data persistent

yes

Snapshots and command logging

In-memory capabilities

Is there an option to define some or all structures to be held in-memory only.

User concepts

Access control

Can implement custom security layer via applications

fine grained access rights according to SQL-standard

Users and roles with access to stored procedures

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

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

Grafana Loki: Architecture Summary and Running in Kubernetes
14 March 2023, hackernoon.com

provided by Google News

Review: Google Bigtable scales with ease
7 September 2016, InfoWorld

provided by Google News

Unveiling Volt Active Data's game-changing approach to limitless app performance
16 October 2023, YourStory

VoltDB Launches Active(N) Lossless Cross Data Center Replication
31 August 2021, PR Newswire

VoltDB Turns to Real-Time Analytics with NewSQL Database
30 January 2014, Datanami

VoltDB Upgrades Power, Security of Its In-Memory Database
1 February 2017, eWeek

VoltDB Adds Geospatial Support, Cross-Site Replication
28 January 2016, The New Stack

provided by Google News

Share this page