DBMS > Apache Impala vs. BaseX vs. MySQL vs. ObjectBox vs. Qdrant

System Properties Comparison Apache Impala vs. BaseX vs. MySQL vs. ObjectBox vs. Qdrant

Editorial information provided by DB-Engines

Name

Description

Analytic DBMS for Hadoop

Light-weight Native XML DBMS with support for XQuery 3.0 and interactive GUI.

Widely used open source RDBMS

Extremely fast embedded database for small devices, IoT and Mobile

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

Primary database model

Relational DBMS

Native XML DBMS

Relational DBMS

Key/Value like access via memcached API

Object oriented DBMS

Vector DBMS

Secondary database models

Document store

Document store
Spatial DBMS

Time Series DBMS

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

Score	13.77
Rank	#40	Overall
	#24	Relational DBMS

Score	1.73
Rank	#142	Overall
	#4	Native XML DBMS

Score	1083.74
Rank	#2	Overall
	#2	Relational DBMS

Score	1.20
Rank	#170	Overall
	#5	Object oriented DBMS

Score	1.16
Rank	#175	Overall
	#6	Vector DBMS

Website

github.com/qdrant/qdrant
qdrant.tech

Technical documentation

impala.apache.org/impala-docs.html

docs.basex.org

dev.mysql.com/doc

docs.objectbox.io

qdrant.tech/documentation

Developer

Apache Software Foundation

Apache top-level project, originally developed by Cloudera

BaseX GmbH

Oracle

since 2010, originally MySQL AB, then Sun

ObjectBox Limited

Qdrant

Initial release

2013

2007

1995

2017

2021

Current release

4.1.0, June 2022

10.7, August 2023

8.3.0, January 2024

License

Commercial or Open Source

Open Source

Apache Version 2

Open Source

BSD license

Open Source

GPL version 2. Commercial licenses with extended functionallity are available

Open Source

Apache License 2.0

Open Source

Apache Version 2.0

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.

Aiven for MySQL: Fully managed MySQL, deployable in the cloud of your choice, with seamless integrations and lightning-fast setup.

Implementation language

C++

Java

C and C++

Rust

Server operating systems

Linux

Linux
OS X
Windows

FreeBSD
Linux
OS X
Solaris
Windows

Android
iOS
Linux
macOS
Windows

Docker
Linux
macOS
Windows

Data scheme

yes

schema-free

yes

schema-free

Typing

predefined data types such as float or date

yes

XQuery supports types

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

Keywords, numberic ranges, geo, full-text

SQL

Support of SQL

SQL-like DML and DDL statements

yes

with proprietary extensions

APIs and other access methods

JDBC
ODBC

Java API
RESTful HTTP API
RESTXQ
WebDAV
XML:DB
XQJ

ADO.NET
JDBC
ODBC
Proprietary native API

Proprietary native API

gRPC
OpenAPI 3.0
RESTful HTTP/JSON API

OpenAPI 3.0

Supported programming languages

All languages supporting JDBC/ODBC

Actionscript
C
C#
Haskell
Java
JavaScript

Node.js
Lisp
Perl
PHP
Python
Qt
Rebol
Ruby
Scala
Visual Basic

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

C
C++
Dart
Go
Java
JavaScript

planned (as of Jan 2019)
Kotlin
Python

planned (as of Jan 2019)
Swift

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

Server-side scripts

Stored procedures

yes

user defined functions and integration of map-reduce

yes

proprietary syntax

Triggers

yes

via events

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

horizontal partitioning, sharding with MySQL Cluster or MySQL Fabric

none

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

selectable replication factor

none

Multi-source replication
Source-replica replication

online/offline synchronization between client and server

Collection-level replication

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

query execution via MapReduce

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency

Immediate Consistency

Eventual Consistency, tunable consistency

Foreign keys

Referential integrity

yes

not for MyISAM storage engine

yes

Transaction concepts

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

multiple readers, single writer

ACID

not for MyISAM storage engine

ACID

Concurrency

Support for concurrent manipulation of data

yes

table locks or row locks depending on storage engine

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

User concepts

Access control

Access rights for users, groups and roles

based on Apache Sentry and Kerberos

Users with fine-grained authorization concept on 4 levels

Users with fine-grained authorization concept

no user groups or roles

yes

Key-based authentication

More information provided by the system vendor

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

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.