DBMS > BoltDB vs. etcd vs. Faircom DB vs. RocksDB vs. Transbase

System Properties Comparison BoltDB vs. etcd vs. Faircom DB vs. RocksDB vs. Transbase

Editorial information provided by DB-Engines

Name

Description

Native high-speed multi-model DBMS for relational and key-value store data simultaneously accessible through SQL and NoSQL APIs.

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

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

Primary database model

Key-value store

Key-value store
Relational DBMS

Key-value 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	7.25
Rank	#54	Overall
	#5	Key-value stores

Score	0.20
Rank	#318	Overall
	#48	Key-value stores
	#141	Relational DBMS

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

Score	0.11
Rank	#341	Overall
	#150	Relational DBMS

Website

github.com/boltdb/bolt

etcd.io
github.com/etcd-io/etcd

www.faircom.com/products/faircom-db

rocksdb.org

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

Technical documentation

etcd.io/docs
github.com/etcd-io/etcd/tree/master/Documentation

docs.faircom.com/docs/en/UUID-7446ae34-a1a7-c843-c894-d5322e395184.html

github.com/facebook/rocksdb/wiki

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

Developer

FairCom Corporation

Facebook, Inc.

Transaction Software GmbH

Initial release

2013

1979

2013

1987

Current release

3.4, August 2019

V12, November 2020

8.11.4, April 2024

Transbase 8.3, 2022

License

Commercial or Open Source

Open Source

MIT License

Open Source

Apache Version 2.0

commercial

Restricted, free version available

Open Source

BSD

commercial

free development license

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

ANSI C, C++

C++

C and C++

Server operating systems

BSD
Linux
OS X
Solaris
Windows

FreeBSD
Linux
Windows

experimental

AIX
FreeBSD
HP-UX
Linux
NetBSD
OS X
QNX
SCO
Solaris
VxWorks
Windows

easily portable to other OSs

Linux

FreeBSD
Linux
macOS
Solaris
Windows

Data scheme

schema-free

schema free, schema optional, schema required, partial schema,

schema-free

yes

Typing

predefined data types such as float or date

yes, ANSI SQL Types, JSON, typed binary structures

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

SQL

Support of SQL

yes, ANSI SQL with proprietary extensions

yes

APIs and other access methods

gRPC
JSON over HTTP

ADO.NET
Direct SQL
JDBC
JPA
ODBC
RESTful HTTP/JSON API
RESTful MQTT/JSON API
RPC

C++ API
Java API

ADO.NET
JDBC
ODBC
Proprietary native API

Supported programming languages

.Net
C
C++
Clojure
Erlang
Go
Haskell
Java
JavaScript (Node.js)
Perl
PHP
Python
R
Ruby
Rust
Scala
Tcl

.Net
C
C#
C++
Java
JavaScript (Node.js and browser)
PHP
Python
Visual Basic

C
C++
Go
Java
Perl
Python
Ruby

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

Server-side scripts

Stored procedures

yes

.Net, JavaScript, C/C++

yes

Triggers

yes, watching key changes

yes

Partitioning methods

Methods for storing different data on different nodes

none

File partitioning, horizontal partitioning, sharding

Customizable business rules for table partitioning

horizontal partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

none

Using Raft consensus algorithm to ensure data replication with strong consistency among multiple replicas.

yes, configurable to be parallel or serial, synchronous or asynchronous, uni-directional or bi-directional, ACID-consistent or eventually consistent (with custom conflict resolution).

yes

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

Eventual Consistency
Immediate Consistency
Tunable consistency per server, database, table, and transaction

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

yes

tunable from ACID to Eventually Consistent

yes

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

Yes, tunable from durable to delayed durability to in-memory

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

Fine grained access rights according to SQL-standard with additional protections for files

fine grained access rights according to SQL-standard

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.