DBMS > Amazon Redshift vs. Machbase Neo vs. Qdrant vs. Spark SQL vs. Sphinx

System Properties Comparison Amazon Redshift vs. Machbase Neo vs. Qdrant vs. Spark SQL vs. Sphinx

Editorial information provided by DB-Engines

Name

Description

Large scale data warehouse service for use with business intelligence tools

TimeSeries DBMS for AIoT and BigData

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

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

Open source search engine for searching in data from different sources, e.g. relational databases

Primary database model

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

Score	16.88
Rank	#35	Overall
	#22	Relational DBMS

Score	0.17
Rank	#337	Overall
	#30	Time Series DBMS

Score	1.28
Rank	#167	Overall
	#6	Vector DBMS

Score	18.04
Rank	#33	Overall
	#20	Relational DBMS

Score	5.95
Rank	#55	Overall
	#5	Search engines

Website

aws.amazon.com/redshift

machbase.com

github.com/qdrant/qdrant
qdrant.tech

spark.apache.org/sql

sphinxsearch.com

Technical documentation

docs.aws.amazon.com/redshift

machbase.com/dbms

qdrant.tech/documentation

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

sphinxsearch.com/docs

Developer

Amazon (based on PostgreSQL)

Machbase

Qdrant

Apache Software Foundation

Sphinx Technologies Inc.

Initial release

2012

2013

2021

2014

2001

Current release

V8.0, August 2023

3.5.0 ( 2.13), September 2023

3.5.1, February 2023

License

Commercial or Open Source

commercial

free test version available

Open Source

Apache Version 2.0

Open Source

Apache 2.0

Open Source

GPL version 2, commercial licence available

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

Rust

Scala

C++

Server operating systems

hosted

Linux
macOS
Windows

Docker
Linux
macOS
Windows

Linux
OS X
Windows

FreeBSD
Linux
NetBSD
OS X
Solaris
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.

Secondary indexes

restricted

yes

Keywords, numberic ranges, geo, full-text

yes

full-text index on all search fields

SQL

Support of SQL

yes

does not fully support an SQL-standard

SQL-like query language

SQL-like DML and DDL statements

SQL-like query language (SphinxQL)

APIs and other access methods

JDBC
ODBC

gRPC
HTTP REST
JDBC
MQTT (Message Queue Telemetry Transport)
ODBC

gRPC
OpenAPI 3.0
RESTful HTTP/JSON API

OpenAPI 3.0

JDBC
ODBC

Proprietary protocol

Supported programming languages

All languages supporting JDBC/ODBC

C
C#
C++
Go
Java
JavaScript
PHP

via ODBC
Python
R

via ODBC
Scala

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

Java
Python
R
Scala

C++

unofficial client library
Java
Perl

unofficial client library
PHP
Python
Ruby

unofficial client library

Server-side scripts

Stored procedures

user defined functions

in Python

Triggers

Partitioning methods

Methods for storing different data on different nodes

Sharding

yes, utilizing Spark Core

Sharding

Partitioning is done manually, search queries against distributed index is supported

Replication methods

Methods for redundantly storing data on multiple nodes

yes

selectable replication factor

Collection-level 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

Foreign keys

Referential integrity

yes

informational only, not enforced by the system

Transaction concepts

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

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

The original contents of fields are not stored in the Sphinx index.

In-memory capabilities

Is there an option to define some or all structures to be held in-memory only.

yes

volatile and lookup table

yes

User concepts

Access control

fine grained access rights according to SQL-standard

simple password-based access control

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.