DBMS > Heroic vs. Machbase Neo vs. Oracle vs. Qdrant vs. VoltDB

System Properties Comparison Heroic vs. Machbase Neo vs. Oracle vs. Qdrant vs. VoltDB

Editorial information provided by DB-Engines

Name

Description

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

TimeSeries DBMS for AIoT and BigData

Widely used RDBMS

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

Distributed In-Memory NewSQL RDBMS

Used for OLTP applications with a high frequency of relatively simple transactions, that can hold all their data in memory

Primary database model

Secondary database models

Document store
Graph DBMS

with Oracle Spatial and Graph
RDF store

with Oracle Spatial and Graph
Spatial DBMS

with Oracle Spatial and Graph
Vector DBMS

since Oracle 23

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

Score	0.46
Rank	#265	Overall
	#22	Time Series DBMS

Score	0.17
Rank	#337	Overall
	#30	Time Series DBMS

Score	1244.08
Rank	#1	Overall
	#1	Relational DBMS

Score	1.28
Rank	#167	Overall
	#6	Vector DBMS

Score	1.47
Rank	#157	Overall
	#73	Relational DBMS

Website

github.com/spotify/heroic

machbase.com

www.oracle.com/database

github.com/qdrant/qdrant
qdrant.tech

www.voltdb.com

Technical documentation

spotify.github.io/heroic

machbase.com/dbms

docs.oracle.com/en/database

qdrant.tech/documentation

docs.voltdb.com

Developer

Spotify

Machbase

Oracle

Qdrant

VoltDB Inc.

Initial release

2014

2013

1980

2021

2010

Current release

V8.0, August 2023

23c, September 2023

11.3, April 2022

License

Commercial or Open Source

Open Source

Apache 2.0

commercial

free test version available

commercial

restricted free version is available

Open Source

Apache Version 2.0

Open Source

AGPL for Community Edition, commercial license for Enterprise, AWS, and Pro Editions

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

Rust

Java, C++

Server operating systems

Linux
macOS
Windows

AIX
HP-UX
Linux
OS X
Solaris
Windows
z/OS

Docker
Linux
macOS
Windows

Linux
OS X

for development

Data scheme

schema-free

yes

Schemaless in JSON and XML columns

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

SQL-like query language

yes

with proprietary extensions

yes

only a subset of SQL 99

APIs and other access methods

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

gRPC
HTTP REST
JDBC
MQTT (Message Queue Telemetry Transport)
ODBC

JDBC
ODBC
ODP.NET
Oracle Call Interface (OCI)

gRPC
OpenAPI 3.0
RESTful HTTP/JSON API

OpenAPI 3.0

Java API
JDBC
RESTful HTTP/JSON API

Supported programming languages

C
C#
C++
Go
Java
JavaScript
PHP

via ODBC
Python
R

via ODBC
Scala

C
C#
C++
Clojure
Cobol
Delphi
Eiffel
Erlang
Fortran
Groovy
Haskell
Java
JavaScript
Lisp
Objective C
OCaml
Perl
PHP
Python
R
Ruby
Scala
Tcl
Visual Basic

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

C#
C++
Erlang

not officially supported
Go
Java
JavaScript

Node.js
PHP
Python

Server-side scripts

Stored procedures

PL/SQL

also stored procedures in Java possible

Java

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

Sharding, horizontal partitioning

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

yes

selectable replication factor

Multi-source replication
Source-replica replication

Collection-level replication

Multi-source replication
Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

can be realized in PL/SQL

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency
Immediate Consistency

Immediate Consistency

Eventual Consistency, tunable consistency

Foreign keys

Referential integrity

yes

FOREIGN KEY constraints are not supported

Transaction concepts

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

ACID

isolation level can be parameterized

ACID

Transactions are executed single-threaded within stored procedures

Concurrency

Support for concurrent manipulation of data

yes

Data access is serialized by the server

Durability

Support for making data persistent

yes

Snapshots and command logging

In-memory capabilities

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

yes

volatile and lookup table

yes

Version 12c introduced the new option 'Oracle Database In-Memory'

yes

User concepts

Access control

simple password-based access control

fine grained access rights according to SQL-standard

Key-based authentication

Users and roles with access to stored procedures

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.