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

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

Editorial information provided by DB-Engines

Name

Description

AI-powered hosted search, recommendation and personalization platform providing tools for both low-code and full-code development

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

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	2.11
Rank	#118	Overall
	#11	Search engines

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

Website

www.coveo.com

github.com/spotify/heroic

machbase.com

www.oracle.com/database

github.com/qdrant/qdrant
qdrant.tech

Technical documentation

docs.coveo.com

spotify.github.io/heroic

machbase.com/dbms

docs.oracle.com/en/database

qdrant.tech/documentation

Developer

Coveo

Spotify

Machbase

Oracle

Qdrant

Initial release

2012

2014

2013

1980

2021

Current release

V8.0, August 2023

23c, September 2023

License

Commercial or Open Source

commercial

Open Source

Apache 2.0

commercial

free test version available

commercial

restricted free version is available

Open Source

Apache Version 2.0

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

C and C++

Rust

Server operating systems

hosted

Linux
macOS
Windows

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

Docker
Linux
macOS
Windows

Data scheme

hybrid - fields need to be configured prior to indexing, but relationships can be exploited at query time without pre-configuration

schema-free

yes

Schemaless in JSON and XML columns

schema-free

Typing

predefined data types such as float or date

yes

Numbers, Strings, Geo, Boolean

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

SQL

Support of SQL

SQL-like query language

yes

with proprietary extensions

APIs and other access methods

RESTful HTTP API

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

Supported programming languages

C#
Java
JavaScript
Python

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

Server-side scripts

Stored procedures

PL/SQL

also stored procedures in Java possible

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

yes

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

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

Immediate Consistency

Eventual Consistency
Immediate Consistency

Immediate Consistency

Eventual Consistency, tunable consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

yes

ACID

isolation level can be parameterized

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

volatile and lookup table

yes

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

yes

User concepts

Access control

granular access controls, API key management, content filters

simple password-based access control

fine grained access rights according to SQL-standard

Key-based authentication

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.