DBMS > Apache Drill vs. MySQL vs. Qdrant vs. Yanza

System Properties Comparison Apache Drill vs. MySQL vs. Qdrant vs. Yanza

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Yanza seems to be discontinued. Therefore it is excluded from the DB-Engines Ranking.

Description

Schema-free SQL Query Engine for Hadoop, NoSQL and Cloud Storage

Widely used open source RDBMS

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

Time Series DBMS for IoT Applications

Primary database model

Document store
Relational DBMS

Relational DBMS

Key/Value like access via memcached API

Vector DBMS

Time Series DBMS

Secondary database models

Document store
Spatial DBMS

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

Score	1.95
Rank	#127	Overall
	#23	Document stores
	#60	Relational DBMS

Score	1083.74
Rank	#2	Overall
	#2	Relational DBMS

Score	1.16
Rank	#175	Overall
	#6	Vector DBMS

Website

drill.apache.org

www.mysql.com

github.com/qdrant/qdrant
qdrant.tech

yanza.com

Technical documentation

drill.apache.org/docs

dev.mysql.com/doc

qdrant.tech/documentation

Developer

Apache Software Foundation

Oracle

since 2010, originally MySQL AB, then Sun

Qdrant

Yanza

Initial release

2012

1995

2021

2015

Current release

1.20.3, January 2023

8.4.0, April 2024

License

Commercial or Open Source

Open Source

Apache Version 2

Open Source

GPL version 2. Commercial licenses with extended functionallity are available

Open Source

Apache Version 2.0

commercial

free version available

Cloud-based only

Only available as a cloud service

but mainly used as a service provided by Yanza

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

Rust

Server operating systems

Linux
OS X
Windows

FreeBSD
Linux
OS X
Solaris
Windows

Docker
Linux
macOS
Windows

Windows

Data scheme

schema-free

yes

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

Keywords, numberic ranges, geo, full-text

SQL

Support of SQL

SQL SELECT statement is SQL:2003 compliant

yes

with proprietary extensions

APIs and other access methods

JDBC
ODBC
RESTful HTTP API

ADO.NET
JDBC
ODBC
Proprietary native API

gRPC
OpenAPI 3.0
RESTful HTTP/JSON API

OpenAPI 3.0

HTTP API

Supported programming languages

C++

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

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

any language that supports HTTP calls

Server-side scripts

Stored procedures

user defined functions

yes

proprietary syntax

Triggers

yes

Timer and event based

Partitioning methods

Methods for storing different data on different nodes

Sharding

horizontal partitioning, sharding with MySQL Cluster or MySQL Fabric

Sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication
Source-replica replication

Collection-level replication

none

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

none

Immediate Consistency

Eventual Consistency, tunable consistency

Immediate Consistency

Foreign keys

Referential integrity

yes

not for MyISAM storage engine

Transaction concepts

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

ACID

not for MyISAM storage engine

Concurrency

Support for concurrent manipulation of data

yes

table locks or row locks depending on storage engine

yes

Durability

Support for making data persistent

Depending on the underlying data source

yes

In-memory capabilities

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

Depending on the underlying data source

yes

User concepts

Access control

Depending on the underlying data source

Users with fine-grained authorization concept

no user groups or roles

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.