DBMS > EsgynDB vs. Hive vs. MySQL vs. Qdrant

System Properties Comparison EsgynDB vs. Hive vs. MySQL vs. Qdrant

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Enterprise-class SQL-on-Hadoop solution, powered by Apache Trafodion

data warehouse software for querying and managing large distributed datasets, built on Hadoop

Widely used open source RDBMS

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

Primary database model

Relational DBMS

Key/Value like access via memcached API

Vector DBMS

Secondary database models

Document store
Spatial DBMS

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

Score	0.16
Rank	#329	Overall
	#146	Relational DBMS

Score	61.17
Rank	#18	Overall
	#12	Relational DBMS

Score	1083.74
Rank	#2	Overall
	#2	Relational DBMS

Score	1.16
Rank	#175	Overall
	#6	Vector DBMS

Website

www.esgyn.cn

hive.apache.org

www.mysql.com

github.com/qdrant/qdrant
qdrant.tech

Technical documentation

cwiki.apache.org/confluence/display/Hive/Home

dev.mysql.com/doc

qdrant.tech/documentation

Developer

Esgyn

Apache Software Foundation

initially developed by Facebook

Oracle

since 2010, originally MySQL AB, then Sun

Qdrant

Initial release

2015

2012

1995

2021

Current release

3.1.3, April 2022

8.4.0, April 2024

License

Commercial or Open Source

commercial

Open Source

Apache Version 2

Open Source

GPL version 2. Commercial licenses with extended functionallity are available

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

Java

C and C++

Rust

Server operating systems

Linux

All OS with a Java VM

FreeBSD
Linux
OS X
Solaris
Windows

Docker
Linux
macOS
Windows

Data scheme

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

yes

SQL-like DML and DDL statements

yes

with proprietary extensions

APIs and other access methods

ADO.NET
JDBC
ODBC

JDBC
ODBC
Thrift

ADO.NET
JDBC
ODBC
Proprietary native API

gRPC
OpenAPI 3.0
RESTful HTTP/JSON API

OpenAPI 3.0

Supported programming languages

All languages supporting JDBC/ODBC/ADO.Net

C++
Java
PHP
Python

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

Server-side scripts

Stored procedures

Java Stored Procedures

yes

user defined functions and integration of map-reduce

yes

proprietary syntax

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

horizontal partitioning, sharding with MySQL Cluster or MySQL Fabric

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication between multi datacenters

selectable replication factor

Multi-source replication
Source-replica replication

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

Immediate Consistency

Eventual Consistency

Immediate Consistency

Eventual Consistency, tunable 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

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

fine grained access rights according to SQL-standard

Access rights for users, groups and roles

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.