DBMS > BoltDB vs. HBase vs. Interbase vs. RocksDB vs. Tarantool

System Properties Comparison BoltDB vs. HBase vs. Interbase vs. RocksDB vs. Tarantool

Editorial information provided by DB-Engines

Name

Description

An embedded key-value store for Go.

Wide-column store based on Apache Hadoop and on concepts of BigTable

Light-weight proven RDBMS

originally from Borland

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

In-memory computing platform with a flexible data schema for efficiently building high-performance applications

Primary database model

Document store
Key-value store
Relational DBMS

Secondary database models

Spatial DBMS

with Tarantool/GIS extension

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

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

Score	30.50
Rank	#26	Overall
	#2	Wide column stores

Score	4.61
Rank	#72	Overall
	#39	Relational DBMS

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

Score	1.72
Rank	#144	Overall
	#25	Document stores
	#25	Key-value stores
	#66	Relational DBMS

Website

github.com/boltdb/bolt

hbase.apache.org

www.embarcadero.com/products/interbase

rocksdb.org

www.tarantool.io

Technical documentation

hbase.apache.org/book.html

docs.embarcadero.com/products/interbase

github.com/facebook/rocksdb/wiki

www.tarantool.io/en/doc

Developer

Apache Software Foundation

Apache top-level project, originally developed by Powerset

Embarcadero

Facebook, Inc.

Initial release

2013

2008

1984

2013

2008

Current release

2.3.4, January 2021

InterBase 2020, December 2019

9.2.1, May 2024

2.10.0, May 2022

License

Commercial or Open Source

Open Source

MIT License

Open Source

Apache version 2

commercial

Open Source

BSD

Open Source

BSD-2, source-available extensions (modules), commercial licenses for Tarantool Enterprise

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

C and C++

Server operating systems

BSD
Linux
OS X
Solaris
Windows

Linux
Unix
Windows

using Cygwin

Android
iOS
Linux
OS X
Windows

Linux

BSD
Linux
macOS

Data scheme

schema-free

schema-free, schema definition possible

yes

schema-free

Flexible data schema: relational definition for tables with ability to store json-like documents in columns

Typing

predefined data types such as float or date

options to bring your own types, AVRO

yes

string, double, decimal, uuid, integer, blob, boolean, datetime

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.

export as XML data possible

Secondary indexes

yes

SQL

Support of SQL

yes

Full-featured ANSI SQL support

APIs and other access methods

Java API
RESTful HTTP API
Thrift

ADO.NET
JDBC
ODBC

C++ API
Java API

Open binary protocol

Supported programming languages

C
C#
C++
Groovy
Java
PHP
Python
Scala

.Net
C
C++
Delphi
Java
Object Pascal
PHP
Ruby

C
C++
Go
Java
Perl
Python
Ruby

C
C#
C++
Erlang
Go
Java
JavaScript
Lua
Perl
PHP
Python
Rust

Server-side scripts

Stored procedures

yes

Coprocessors in Java

yes

Interbase procedure and trigger language

Lua, C and SQL stored procedures

Triggers

yes

yes, before/after data modification events, on replication events, client session events

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

none

horizontal partitioning

Sharding, partitioned with virtual buckets by user defined affinity key. Live resharding for scale up and scale down without maintenance downtime.

Replication methods

Methods for redundantly storing data on multiple nodes

none

Multi-source replication
Source-replica replication

Interbase Change Views

yes

Asynchronous replication with multi-master option
Configurable replication topology (full-mesh, chain, star)
Synchronous quorum replication (with Raft)

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

none

Immediate Consistency or Eventual Consistency

Immediate Consistency

Casual consistency across sharding partitions
Eventual consistency within replicaset partition

when using asyncronous replication
Immediate Consistency within single instance
Sequential consistency including linearizable read within replicaset partition

when using Raft

Foreign keys

Referential integrity

yes

Transaction concepts

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

yes

Single row ACID (across millions of columns)

ACID

yes

ACID, with serializable isolation and linearizable read (within partition); Configurable MVCC (within partition); No cross-shard distributed transactions

Concurrency

Support for concurrent manipulation of data

yes

Multiversion concurreny control

yes

yes, cooperative multitasking

Durability

Support for making data persistent

yes

yes, write ahead logging

In-memory capabilities

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

yes

yes, full featured in-memory storage engine with persistence

User concepts

Access control

Access Control Lists (ACL) for RBAC, integration with Apache Ranger for RBAC & ABAC

fine grained access rights according to SQL-standard

Access Control Lists
Mutual TLS authentication for Tarantol Enterprise
Password based authentication
Role-based access control (RBAC) and LDAP for Tarantol Enterprise
Users and Roles

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.