DBMS > Google Cloud Spanner vs. MySQL vs. Qdrant vs. SAP Advantage Database Server

System Properties Comparison Google Cloud Spanner vs. MySQL vs. Qdrant vs. SAP Advantage Database Server

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

SAP Advantage Database Server seems to be discontinued. Therefore it is excluded from the DB-Engines Ranking.

Description

A horizontally scalable, globally consistent, relational database service. It is the externalization of the core Google database that runs the biggest aspects of Google, like Ads and Google Play.

Widely used open source RDBMS

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

Low-cost RDBMS with access to ISAM and FoxPro data structures

Primary database model

Relational DBMS

Key/Value like access via memcached API

Vector DBMS

Relational DBMS

Secondary database models

Document store
Spatial DBMS

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

Score	2.89
Rank	#105	Overall
	#53	Relational DBMS

Score	1087.72
Rank	#2	Overall
	#2	Relational DBMS

Score	1.23
Rank	#171	Overall
	#6	Vector DBMS

Website

cloud.google.com/spanner

www.mysql.com

github.com/qdrant/qdrant
qdrant.tech

www.sap.com/products/advantage-database-server.html

Technical documentation

cloud.google.com/spanner/docs

dev.mysql.com/doc

qdrant.tech/documentation

Developer

Google

Oracle

since 2010, originally MySQL AB, then Sun

Qdrant

Sybase, SAP

Initial release

2017

1995

2021

1993

Current release

8.3.0, January 2024

License

Commercial or Open Source

commercial

Open Source

GPL version 2. Commercial licenses with extended functionallity are available

Open Source

Apache Version 2.0

commercial

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.

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

hosted

FreeBSD
Linux
OS X
Solaris
Windows

Docker
Linux
macOS
Windows

Linux
Windows

Data scheme

yes

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

Query statements complying to ANSI 2011

yes

with proprietary extensions

yes

APIs and other access methods

gRPC (using protocol buffers) API
JDBC

At present, JDBC supports read-only queries. No support for DDL or DML statements.
RESTful HTTP API

ADO.NET
JDBC
ODBC
Proprietary native API

gRPC
OpenAPI 3.0
RESTful HTTP/JSON API

OpenAPI 3.0

.NET Client API
ADO.NET
JDBC
ODBC
OLE DB

Supported programming languages

Go
Java
JavaScript (Node.js)
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

Delphi
Perl
PHP

Server-side scripts

Stored procedures

yes

proprietary syntax

yes

Triggers

yes

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 with 3 replicas for regional instances.

Multi-source replication
Source-replica replication

Collection-level replication

Multi-source replication

CONFLICT Trigger to resolve replication conflicts
Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

using Google Cloud Dataflow

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency, tunable consistency

Immediate Consistency

Foreign keys

Referential integrity

yes

by using interleaved tables, this features focuses more on performance improvements than on referential integrity

yes

not for MyISAM storage engine

yes

Transaction concepts

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

ACID

Strict serializable isolation

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

caching of (temporary) tables can be configured

User concepts

Access control

Access rights for users, groups and roles based on Google Cloud Identity and Access Management (IAM)

Users with fine-grained authorization concept

no user groups or roles

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.