DBMS > Heroic vs. ObjectBox vs. RocksDB vs. Sadas Engine vs. Vitess

System Properties Comparison Heroic vs. ObjectBox vs. RocksDB vs. Sadas Engine vs. Vitess

Editorial information provided by DB-Engines

Name

Description

Time Series DBMS built at Spotify based on Cassandra or Google Cloud Bigtable, and ElasticSearch

Extremely fast embedded database for small devices, IoT and Mobile

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

SADAS Engine is a columnar DBMS specifically designed for high performance in data warehouse environments

Scalable, distributed, cloud-native DBMS, extending MySQL

Primary database model

Secondary database models

Time Series DBMS

Document store
Spatial DBMS

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

Score	0.51
Rank	#255	Overall
	#21	Time Series DBMS

Score	1.20
Rank	#170	Overall
	#5	Object oriented DBMS

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

Score	0.00
Rank	#383	Overall
	#158	Relational DBMS

Score	0.82
Rank	#209	Overall
	#97	Relational DBMS

Website

github.com/spotify/heroic

Technical documentation

spotify.github.io/heroic

docs.objectbox.io

github.com/facebook/rocksdb/wiki

www.sadasengine.com/en/sadas-engine-download-free-trial-and-documentation/#documentation

vitess.io/docs

Developer

Spotify

ObjectBox Limited

Facebook, Inc.

SADAS s.r.l.

The Linux Foundation, PlanetScale

Initial release

2014

2017

2013

2006

2013

Current release

8.11.4, April 2024

8.0

15.0.2, December 2022

License

Commercial or Open Source

Open Source

Apache 2.0

Open Source

Apache License 2.0

Open Source

BSD

commercial

free trial version available

Open Source

Apache Version 2.0, commercial licenses 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++

C++

Server operating systems

Android
iOS
Linux
macOS
Windows

Linux

AIX
Linux
Windows

Docker
Linux
macOS

Data scheme

schema-free

yes

schema-free

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.

Secondary indexes

yes

via Elasticsearch

yes

SQL

Support of SQL

yes

with proprietary extensions

APIs and other access methods

HQL (Heroic Query Language, a JSON-based language)
HTTP API

Proprietary native API

C++ API
Java API

JDBC
ODBC
Proprietary protocol

ADO.NET
JDBC
MySQL protocol
ODBC

Supported programming languages

C
C++
Dart
Go
Java
JavaScript

planned (as of Jan 2019)
Kotlin
Python

planned (as of Jan 2019)
Swift

C
C++
Go
Java
Perl
Python
Ruby

.Net
C
C#
C++
Groovy
Java
PHP
Python

Ada
C
C#
C++
D
Delphi
Eiffel
Erlang
Haskell
Java
JavaScript (Node.js)
Objective-C
OCaml
Perl
PHP
Python
Ruby
Scheme
Tcl

Server-side scripts

Stored procedures

yes

proprietary syntax

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

horizontal partitioning

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

yes

online/offline synchronization between client and server

yes

none

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

Eventual Consistency
Immediate Consistency

Immediate Consistency

Eventual Consistency across shards
Immediate Consistency within a shard

Foreign keys

Referential integrity

yes

not for MyISAM storage engine

Transaction concepts

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

ACID

yes

ACID at shard level

Concurrency

Support for concurrent manipulation of data

yes

table locks or row locks depending on storage engine

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

managed by 'Learn by Usage'

yes

User concepts

Access control

yes

Access rights for users, groups and roles according to SQL-standard

Users with fine-grained authorization concept

no user groups or roles

More information provided by the system vendor

News

On-device Vector Database for Dart/Flutter
21 May 2024

The first On-Device Vector Database: ObjectBox 4.0
16 May 2024

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

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.