DBMS > Amazon Neptune vs. MySQL vs. Percona Server for MySQL vs. Qdrant

System Properties Comparison Amazon Neptune vs. MySQL vs. Percona Server for MySQL vs. Qdrant

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Fast, reliable graph database built for the cloud

Widely used open source RDBMS

Enhanced drop-in replacement for MySQL based on XtraDB or TokuDB storage engines with improved performance and additional diagnostic and management features.

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

Primary database model

Graph DBMS
RDF store

Relational DBMS

Key/Value like access via memcached API

Relational DBMS

Vector DBMS

Secondary database models

Document store
Spatial DBMS

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

Score	2.20
Rank	#113	Overall
	#9	Graph DBMS
	#5	RDF stores

Score	1029.49
Rank	#2	Overall
	#2	Relational DBMS

Score	2.06
Rank	#118	Overall
	#57	Relational DBMS

Score	1.53
Rank	#145	Overall
	#7	Vector DBMS

Website

aws.amazon.com/neptune

www.mysql.com

www.percona.com/software/mysql-database/percona-server

github.com/qdrant/qdrant
qdrant.tech

Technical documentation

aws.amazon.com/neptune/developer-resources

dev.mysql.com/doc

www.percona.com/downloads/Percona-Server-LATEST

qdrant.tech/documentation

Developer

Amazon

Oracle

since 2010, originally MySQL AB, then Sun

Percona

Qdrant

Initial release

2017

1995

2008

2021

Current release

9.0.0, July 2024

8.0.36-28, 2024

License

Commercial or Open Source

commercial

Open Source

GPL version 2. Commercial licenses with extended functionallity are available

Open Source

GPL version 2

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

C and C++

Rust

Server operating systems

hosted

FreeBSD
Linux
OS X
Solaris
Windows

Linux

Docker
Linux
macOS
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

yes

with proprietary extensions

yes

APIs and other access methods

OpenCypher
RDF 1.1 / SPARQL 1.1
TinkerPop Gremlin

ADO.NET
JDBC
ODBC
Proprietary native API

ADO.NET
JDBC
ODBC

gRPC
OpenAPI 3.0
RESTful HTTP/JSON API

OpenAPI 3.0

Supported programming languages

C#
Go
Java
JavaScript
PHP
Python
Ruby
Scala

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

Ada
C
C#
C++
D
Eiffel
Erlang
Haskell
Java
Objective-C
OCaml
Perl
PHP
Python
Ruby
Scheme
Tcl

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

Server-side scripts

Stored procedures

yes

proprietary syntax

yes

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

none

horizontal partitioning, sharding with MySQL Cluster or MySQL Fabric

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-availability zones high availability, asynchronous replication for up to 15 read replicas within a single region. Global database clusters consists of a primary write DB cluster in one region, and up to five secondary read DB clusters in different regions. Each secondary region can have up to 16 reader instances.

Multi-source replication
Source-replica replication

Multi-source replication
Source-replica replication
XtraDB Cluster

Collection-level replication

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency, tunable consistency

Foreign keys

Referential integrity

yes

Relationships in graphs

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

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

with encyption-at-rest

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 and roles can be defined via the AWS Identity and Access Management (IAM)

Users with fine-grained authorization concept

no user groups or 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.