DBMS > Amazon Redshift vs. Apache Impala vs. Qdrant vs. Sphinx

System Properties Comparison Amazon Redshift vs. Apache Impala vs. Qdrant vs. Sphinx

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Large scale data warehouse service for use with business intelligence tools

Analytic DBMS for Hadoop

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

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

Primary database model

Relational DBMS

Vector DBMS

Search engine

Secondary database models

Document store

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

Score	17.94
Rank	#34	Overall
	#21	Relational DBMS

Score	13.77
Rank	#40	Overall
	#24	Relational DBMS

Score	1.16
Rank	#175	Overall
	#6	Vector DBMS

Score	5.98
Rank	#56	Overall
	#5	Search engines

Website

aws.amazon.com/redshift

impala.apache.org

github.com/qdrant/qdrant
qdrant.tech

sphinxsearch.com

Technical documentation

docs.aws.amazon.com/redshift

impala.apache.org/impala-docs.html

qdrant.tech/documentation

sphinxsearch.com/docs

Developer

Amazon (based on PostgreSQL)

Apache Software Foundation

Apache top-level project, originally developed by Cloudera

Qdrant

Sphinx Technologies Inc.

Initial release

2012

2013

2021

2001

Current release

4.1.0, June 2022

3.5.1, February 2023

License

Commercial or Open Source

commercial

Open Source

Apache Version 2

Open Source

Apache Version 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

C++

Rust

C++

Server operating systems

hosted

Linux

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

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 DML and DDL statements

SQL-like query language (SphinxQL)

APIs and other access methods

JDBC
ODBC

gRPC
OpenAPI 3.0
RESTful HTTP/JSON API

OpenAPI 3.0

Proprietary protocol

Supported programming languages

All languages supporting JDBC/ODBC

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

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

yes

user defined functions and integration of map-reduce

Triggers

Partitioning methods

Methods for storing different data on different nodes

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

yes

query execution via MapReduce

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual 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

User concepts

Access control

fine grained access rights according to SQL-standard

Access rights for users, groups and roles

based on Apache Sentry and Kerberos

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.