DBMS > Postgres-XL vs. Qdrant vs. RocksDB vs. SAP Advantage Database Server vs. Spark SQL

System Properties Comparison Postgres-XL vs. Qdrant vs. RocksDB vs. SAP Advantage Database Server vs. Spark SQL

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

Based on PostgreSQL enhanced with MPP and write-scale-out cluster features

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

Embeddable persistent key-value store optimized for fast storage (flash and RAM)

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

Spark SQL is a component on top of 'Spark Core' for structured data processing

Primary database model

Secondary database models

Document store
Spatial DBMS

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

Score	0.53
Rank	#254	Overall
	#117	Relational DBMS

Score	1.28
Rank	#167	Overall
	#7	Vector DBMS

Score	3.41
Rank	#86	Overall
	#11	Key-value stores

Score	18.04
Rank	#33	Overall
	#20	Relational DBMS

Website

www.postgres-xl.org

github.com/qdrant/qdrant
qdrant.tech

rocksdb.org

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

spark.apache.org/sql

Technical documentation

www.postgres-xl.org/documentation

qdrant.tech/documentation

github.com/facebook/rocksdb/wiki

spark.apache.org/docs/latest/sql-programming-guide.html

Developer

Qdrant

Facebook, Inc.

Sybase, SAP

Apache Software Foundation

Initial release

2014

since 2012, originally named StormDB

2021

2013

1993

2014

Current release

10 R1, October 2018

9.2.1, May 2024

3.5.0 ( 2.13), September 2023

License

Commercial or Open Source

Open Source

Mozilla public license

Open Source

Apache Version 2.0

Open Source

BSD

commercial

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.

Implementation language

Rust

C++

Scala

Server operating systems

Linux
macOS

Docker
Linux
macOS
Windows

Linux

Linux
Windows

Linux
OS X
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

XML type, but no XML query functionality

Secondary indexes

yes

Keywords, numberic ranges, geo, full-text

yes

SQL

Support of SQL

yes

distributed, parallel query execution

yes

SQL-like DML and DDL statements

APIs and other access methods

ADO.NET
JDBC
native C library
ODBC
streaming API for large objects

gRPC
OpenAPI 3.0
RESTful HTTP/JSON API

OpenAPI 3.0

C++ API
Java API

.NET Client API
ADO.NET
JDBC
ODBC
OLE DB

JDBC
ODBC

Supported programming languages

.Net
C
C++
Delphi
Erlang
Java
JavaScript (Node.js)
Perl
PHP
Python
Tcl

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

C
C++
Go
Java
Perl
Python
Ruby

Delphi
Perl
PHP

Java
Python
R
Scala

Server-side scripts

Stored procedures

user defined functions

yes

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

horizontal partitioning

Sharding

horizontal partitioning

none

yes, utilizing Spark Core

Replication methods

Methods for redundantly storing data on multiple nodes

Collection-level replication

yes

Multi-source replication

CONFLICT Trigger to resolve replication conflicts
Source-replica replication

none

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

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

MVCC

yes

ACID

Concurrency

Support for concurrent manipulation of data

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

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.