DBMS > Heroic vs. IBM Cloudant vs. Qdrant vs. RocksDB vs. Tibero

System Properties Comparison Heroic vs. IBM Cloudant vs. Qdrant vs. RocksDB vs. Tibero

Editorial information provided by DB-Engines

Name

Description

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

Database as a Service offering based on Apache CouchDB

A high-performance vector database with neural network or semantic-based matching

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

A secure RDBMS, designed for easy portability from Oracle

Primary database model

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

Score	0.51
Rank	#255	Overall
	#21	Time Series DBMS

Score	2.68
Rank	#106	Overall
	#20	Document stores

Score	1.16
Rank	#175	Overall
	#6	Vector DBMS

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

Score	1.78
Rank	#140	Overall
	#64	Relational DBMS

Website

github.com/spotify/heroic

www.ibm.com/products/cloudant

github.com/qdrant/qdrant
qdrant.tech

rocksdb.org

us.tmaxsoft.com/products/tibero

Technical documentation

spotify.github.io/heroic

cloud.ibm.com/docs/Cloudant

qdrant.tech/documentation

github.com/facebook/rocksdb/wiki

technet.tmaxsoft.com/upload/download/online/tibero/pver-20150504-000002/index.html

Developer

Spotify

IBM, Apache Software Foundation

IBM acquired Cloudant in February 2014

Qdrant

Facebook, Inc.

TmaxSoft

Initial release

2014

2010

2021

2013

2003

Current release

8.11.4, April 2024

6, April 2015

License

Commercial or Open Source

Open Source

Apache 2.0

commercial

Open Source

Apache Version 2.0

Open Source

BSD

commercial

Cloud-based only

Only available as a cloud service

yes

DBaaS offerings (sponsored links)

Database as a Service

Providers of DBaaS offerings, please contact us to be listed.

Implementation language

Java

Erlang

Rust

C++

C and Assembler

Server operating systems

hosted

Docker
Linux
macOS
Windows

Linux

AIX
HP-UX
Linux
Solaris
Windows

Data scheme

schema-free

yes

Typing

predefined data types such as float or date

yes

Numbers, Strings, Geo, Boolean

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.

yes

Secondary indexes

yes

via Elasticsearch

yes

Keywords, numberic ranges, geo, full-text

yes

SQL

Support of SQL

yes

APIs and other access methods

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

RESTful HTTP/JSON API

gRPC
OpenAPI 3.0
RESTful HTTP/JSON API

OpenAPI 3.0

C++ API
Java API

JDBC
ODBC
ODP.NET
Oracle Call Interface (OCI)
Tibero CLI

Supported programming languages

C#
Java
JavaScript
Objective-C
PHP
Ruby

.Net
Go
Java
JavaScript (Node.js)
Python
Rust

C
C++
Go
Java
Perl
Python
Ruby

C
C#
C++
Cobol
Java
Objective-C
Perl
PHP
Python
Ruby
Visual Basic

Server-side scripts

Stored procedures

View functions (Map-Reduce) in JavaScript

Persistent Stored Procedure (PSM)

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

horizontal partitioning

by range, hash, list or composite

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Multi-source replication
Source-replica replication

Collection-level replication

yes

Multi-source replication
Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency
Immediate Consistency

Eventual Consistency

Eventual Consistency, tunable consistency

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

atomic operations within a document possible

yes

ACID

Concurrency

Support for concurrent manipulation of data

yes

Optimistic locking

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

planned for next version

User concepts

Access control

Access rights for users can be defined per database

Key-based authentication

fine grained access rights according to SQL-standard (SQL 92, SQL 99)

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.