DBMS > HBase vs. ObjectBox vs. QuestDB vs. RocksDB vs. STSdb

System Properties Comparison HBase vs. ObjectBox vs. QuestDB vs. RocksDB vs. STSdb

Editorial information provided by DB-Engines

Name

Description

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

Extremely fast embedded database for small devices, IoT and Mobile

A high performance open source SQL database for time series data

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

Key-Value Store with special method for indexing

optimized for high performance using a special indexing method

Primary database model

Secondary database models

Time Series DBMS

Relational DBMS

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

Score	30.50
Rank	#26	Overall
	#2	Wide column stores

Score	1.20
Rank	#170	Overall
	#5	Object oriented DBMS

Score	2.52
Rank	#109	Overall
	#9	Time Series DBMS

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

Score	0.04
Rank	#360	Overall
	#52	Key-value stores

Website

github.com/STSSoft/STSdb4

Technical documentation

hbase.apache.org/book.html

docs.objectbox.io

questdb.io/docs

github.com/facebook/rocksdb/wiki

Developer

Apache Software Foundation

Apache top-level project, originally developed by Powerset

ObjectBox Limited

QuestDB Technology Inc

Facebook, Inc.

STS Soft SC

Initial release

2008

2017

2014

2013

2011

Current release

2.3.4, January 2021

8.11.4, April 2024

4.0.8, September 2015

License

Commercial or Open Source

Open Source

Apache version 2

Open Source

Apache License 2.0

Open Source

Apache 2.0

Open Source

BSD

Open Source

GPLv2, commercial license available

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 (Zero-GC), C++, Rust

C++

Server operating systems

Linux
Unix
Windows

using Cygwin

Android
iOS
Linux
macOS
Windows

Linux
macOS
Windows

Linux

Windows

Data scheme

schema-free, schema definition possible

yes

schema-free via InfluxDB Line Protocol

schema-free

yes

Typing

predefined data types such as float or date

options to bring your own types, AVRO

yes

primitive types and user defined types (classes)

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 with time-series extensions

APIs and other access methods

Java API
RESTful HTTP API
Thrift

Proprietary native API

HTTP REST
InfluxDB Line Protocol (TCP/UDP)
JDBC
PostgreSQL wire protocol

C++ API
Java API

.NET Client API

Supported programming languages

C
C#
C++
Groovy
Java
PHP
Python
Scala

C
C++
Dart
Go
Java
JavaScript

planned (as of Jan 2019)
Kotlin
Python

planned (as of Jan 2019)
Swift

PostgreSQL driver
C++
Go
Java
JavaScript (Node.js)
Python
Rust

over HTTP

C
C++
Go
Java
Perl
Python
Ruby

C#
Java

Server-side scripts

Stored procedures

yes

Coprocessors in Java

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

horizontal partitioning (by timestamps)

horizontal partitioning

none

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication
Source-replica replication

online/offline synchronization between client and server

Source-replica replication with eventual consistency

yes

none

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency or Eventual Consistency

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

Single row ACID (across millions of columns)

ACID

ACID for single-table writes

yes

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

In-memory capabilities

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

yes

through memory mapped files

yes

User concepts

Access control

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

yes

More information provided by the system vendor

Specific characteristics

Relational model with native time series support Column-based storage and time partitioned...
» more

Competitive advantages

High ingestion throughput: peak of 4M rows/sec (TSBS Benchmark) Code optimizations...
» more

Typical application scenarios

Financial tick data Industrial IoT Application Metrics Monitoring
» more

Key customers

Banks & Hedge funds, Yahoo, OKX, Airbus, Aquis Exchange, Net App, Cloudera, Airtel,...
» more

Licensing and pricing models

Open source Apache 2.0 QuestDB Enterprise QuestDB Cloud
» more

News

Edge AI: The era of on-device AI
23 April 2024

In-Memory Database Use Cases
15 February 2024

Data Viewer for Objects – announcing ObjectBox Admin
14 November 2023

Vector Databases for Edge AI
9 August 2023

Vector Database Release for Flutter / Dart + Python
13 June 2023

Build your own resource monitor with QuestDB and Grafana
6 May 2024

Does "vpmovzxbd" Scare You? Here's Why it Doesn't Have To
12 April 2024

Create an ADS-B flight radar with QuestDB and a Raspberry Pi
8 April 2024

Build a temperature IoT sensor with Raspberry Pi Pico & QuestDB
5 April 2024

Create an IoT server with QuestDB and a Raspberry Pi
4 April 2024

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.