DBMS > MySQL vs. Oracle vs. Qdrant vs. Trafodion

System Properties Comparison MySQL vs. Oracle vs. Qdrant vs. Trafodion

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Apache Trafodion has been retired in 2021. Therefore it is excluded from the DB-Engines Ranking.

Description

Widely used open source RDBMS

Widely used RDBMS

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

Transactional SQL-on-Hadoop DBMS

Primary database model

Relational DBMS

Key/Value like access via memcached API

Relational DBMS

Vector DBMS

Relational DBMS

Secondary database models

Document store
Spatial DBMS

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	1083.74
Rank	#2	Overall
	#2	Relational DBMS

Score	1236.29
Rank	#1	Overall
	#1	Relational DBMS

Score	1.16
Rank	#175	Overall
	#6	Vector DBMS

Website

www.mysql.com

www.oracle.com/database

github.com/qdrant/qdrant
qdrant.tech

trafodion.apache.org

Technical documentation

dev.mysql.com/doc

docs.oracle.com/en/database

qdrant.tech/documentation

trafodion.apache.org/documentation.html

Developer

Oracle

since 2010, originally MySQL AB, then Sun

Oracle

Qdrant

Apache Software Foundation, originally developed by HP

Initial release

1995

1980

2021

2014

Current release

8.4.0, April 2024

23c, September 2023

2.3.0, February 2019

License

Commercial or Open Source

Open Source

GPL version 2. Commercial licenses with extended functionallity are available

commercial

restricted free version is available

Open Source

Apache Version 2.0

Open Source

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

Rust

C++, Java

Server operating systems

FreeBSD
Linux
OS X
Solaris
Windows

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

Docker
Linux
macOS
Windows

Linux

Data scheme

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

Keywords, numberic ranges, geo, full-text

yes

SQL

Support of SQL

yes

with proprietary extensions

yes

with proprietary extensions

yes

APIs and other access methods

ADO.NET
JDBC
ODBC
Proprietary native API

JDBC
ODBC
ODP.NET
Oracle Call Interface (OCI)

gRPC
OpenAPI 3.0
RESTful HTTP/JSON API

OpenAPI 3.0

ADO.NET
JDBC
ODBC

Supported programming languages

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

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

All languages supporting JDBC/ODBC/ADO.Net

Server-side scripts

Stored procedures

yes

proprietary syntax

PL/SQL

also stored procedures in Java possible

Java Stored Procedures

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

horizontal partitioning, sharding with MySQL Cluster or MySQL Fabric

Sharding, horizontal partitioning

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication
Source-replica replication

Collection-level replication

yes, via HBase

MapReduce

Offers an API for user-defined Map/Reduce methods

can be realized in PL/SQL

yes

via user defined functions and HBase

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency, tunable consistency

Immediate 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

ACID

not for MyISAM storage engine

ACID

isolation level can be parameterized

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

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

yes

User concepts

Access control

Users with fine-grained authorization concept

no user groups or roles

fine grained access rights according to SQL-standard

Key-based authentication

fine grained access rights according to SQL-standard

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.