DBMS > Apache Impala vs. BoltDB vs. HBase vs. RocksDB vs. Tarantool

System Properties Comparison Apache Impala vs. BoltDB vs. HBase vs. RocksDB vs. Tarantool

Editorial information provided by DB-Engines

Name

Description

Analytic DBMS for Hadoop

An embedded key-value store for Go.

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

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

Document store

Spatial DBMS

with Tarantool/GIS extension

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

Score	13.77
Rank	#40	Overall
	#24	Relational DBMS

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

Score	30.50
Rank	#26	Overall
	#2	Wide column stores

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

impala.apache.org

github.com/boltdb/bolt

hbase.apache.org

rocksdb.org

www.tarantool.io

Technical documentation

impala.apache.org/impala-docs.html

hbase.apache.org/book.html

github.com/facebook/rocksdb/wiki

www.tarantool.io/en/doc

Developer

Apache Software Foundation

Apache top-level project, originally developed by Cloudera

Apache Software Foundation

Apache top-level project, originally developed by Powerset

Facebook, Inc.

Initial release

2013

2008

2013

2008

Current release

4.1.0, June 2022

2.3.4, January 2021

8.11.4, April 2024

2.10.0, May 2022

License

Commercial or Open Source

Open Source

Apache Version 2

Open Source

MIT License

Open Source

Apache version 2

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

C++

Java

C++

C and C++

Server operating systems

Linux

BSD
Linux
OS X
Solaris
Windows

Linux
Unix
Windows

using Cygwin

Linux

BSD
Linux
macOS

Data scheme

yes

schema-free

schema-free, schema definition possible

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

yes

options to bring your own types, AVRO

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.

Secondary indexes

yes

SQL

Support of SQL

SQL-like DML and DDL statements

Full-featured ANSI SQL support

APIs and other access methods

JDBC
ODBC

Java API
RESTful HTTP API
Thrift

C++ API
Java API

Open binary protocol

Supported programming languages

All languages supporting JDBC/ODBC

C
C#
C++
Groovy
Java
PHP
Python
Scala

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

user defined functions and integration of map-reduce

yes

Coprocessors in Java

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

Sharding

none

Sharding

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

selectable replication factor

none

Multi-source replication
Source-replica replication

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

query execution via MapReduce

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency

none

Immediate Consistency or Eventual 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)

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

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 rights for users, groups and roles

based on Apache Sentry and Kerberos

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

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.