DBMS > Amazon Redshift vs. Apache Phoenix vs. Manticore Search vs. Qdrant

System Properties Comparison Amazon Redshift vs. Apache Phoenix vs. Manticore Search vs. Qdrant

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

A scale-out RDBMS with evolutionary schema built on Apache HBase

Multi-storage database for search, including full-text search.

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

Primary database model

Relational DBMS

Search engine

Vector DBMS

Secondary database models

Time Series DBMS

using the Manticore Columnar Library

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

Score	17.94
Rank	#34	Overall
	#21	Relational DBMS

Score	1.97
Rank	#126	Overall
	#59	Relational DBMS

Score	0.22
Rank	#312	Overall
	#21	Search engines

Score	1.16
Rank	#175	Overall
	#6	Vector DBMS

Website

aws.amazon.com/redshift

phoenix.apache.org

manticoresearch.com

github.com/qdrant/qdrant
qdrant.tech

Technical documentation

docs.aws.amazon.com/redshift

phoenix.apache.org

manual.manticoresearch.com

qdrant.tech/documentation

Developer

Amazon (based on PostgreSQL)

Apache Software Foundation

Manticore Software

Qdrant

Initial release

2012

2014

2017

2021

Current release

5.0-HBase2, July 2018 and 4.15-HBase1, December 2019

6.0, February 2023

License

Commercial or Open Source

commercial

Open Source

Apache Version 2.0

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

Java

C++

Rust

Server operating systems

hosted

Linux
Unix
Windows

FreeBSD
Linux
macOS
Windows

Docker
Linux
macOS
Windows

Data scheme

yes

late-bound, schema-on-read capabilities

Fixed schema

schema-free

Typing

predefined data types such as float or date

yes

Int, Bigint, Float, Timestamp, Bit, Int array, Bigint array, JSON, Boolean

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.

Can index from XML

Secondary indexes

restricted

yes

full-text index on all search fields

yes

Keywords, numberic ranges, geo, full-text

SQL

Support of SQL

yes

does not fully support an SQL-standard

yes

SQL-like query language

APIs and other access methods

JDBC
ODBC

JDBC

Binary API
RESTful HTTP/JSON API
RESTful HTTP/SQL API
SQL over MySQL

gRPC
OpenAPI 3.0
RESTful HTTP/JSON API

OpenAPI 3.0

Supported programming languages

All languages supporting JDBC/ODBC

C
C#
C++
Go
Groovy
Java
PHP
Python
Scala

Elixir
Go
Java
JavaScript (Node.js)
Perl
PHP
Python

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

Server-side scripts

Stored procedures

user defined functions

in Python

user defined functions

Triggers

Partitioning methods

Methods for storing different data on different nodes

Sharding

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

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Multi-source replication
Source-replica replication

Synchronous replication based on Galera library

Collection-level replication

MapReduce

Offers an API for user-defined Map/Reduce methods

Hadoop integration

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Immediate Consistency or 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

yes

isolated transactions for atomic changes and binary logging for safe writes

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 Manticore index.

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

fine grained access rights according to SQL-standard

Access Control Lists (using HBase ACL) for RBAC, integration with Apache Ranger for RBAC & ABAC, multi-tenancy

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.