DBMS > BoltDB vs. Stardog vs. Transbase vs. VoltDB

System Properties Comparison BoltDB vs. Stardog vs. Transbase vs. VoltDB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Enterprise Knowledge Graph platform and graph DBMS with high availability, high performance reasoning, and virtualization

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

Graph DBMS
RDF store

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	2.02
Rank	#123	Overall
	#11	Graph DBMS
	#6	RDF stores

Score	0.11
Rank	#341	Overall
	#150	Relational DBMS

Score	1.44
Rank	#158	Overall
	#73	Relational DBMS

Website

github.com/boltdb/bolt

www.stardog.com

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

www.voltdb.com

Technical documentation

docs.stardog.com

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

docs.voltdb.com

Developer

Stardog-Union

Transaction Software GmbH

VoltDB Inc.

Initial release

2013

2010

1987

2010

Current release

7.3.0, May 2020

Transbase 8.3, 2022

11.3, April 2022

License

Commercial or Open Source

Open Source

MIT License

commercial

60-day fully-featured trial license; 1-year fully-featured non-commercial use license for academics/students

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

Linux
macOS
Windows

FreeBSD
Linux
macOS
Solaris
Windows

Linux
OS X

for development

Data scheme

schema-free

schema-free and OWL/RDFS-schema support

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.

Import/export of XML data possible

Secondary indexes

yes

supports real-time indexing in full-text and geospatial

yes

SQL

Support of SQL

Yes, compatible with all major SQL variants through dedicated BI/SQL Server

yes

only a subset of SQL 99

APIs and other access methods

GraphQL query language
HTTP API
Jena RDF API
OWL
RDF4J API
Sesame REST HTTP Protocol
SNARL
SPARQL
Spring Data
Stardog Studio
TinkerPop 3

ADO.NET
JDBC
ODBC
Proprietary native API

Java API
JDBC
RESTful HTTP/JSON API

Supported programming languages

.Net
Clojure
Groovy
Java
JavaScript
Python
Ruby

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

user defined functions and aggregates, HTTP Server extensions in Java

yes

Java

Triggers

yes

via event handlers

yes

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

none

Multi-source replication in HA-Cluster

Source-replica replication

Multi-source replication
Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

none

Immediate Consistency in HA-Cluster

Immediate Consistency

Foreign keys

Referential integrity

yes

relationships in graphs

yes

FOREIGN KEY constraints are not supported

Transaction concepts

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

yes

ACID

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.

yes

User concepts

Access control

Access rights for users and roles

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

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

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