DBMS > Amazon Redshift vs. Manticore Search vs. Qdrant vs. Tkrzw

System Properties Comparison Amazon Redshift vs. Manticore Search vs. Qdrant vs. Tkrzw

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

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

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

A concept of libraries, allowing an application program to store and query key-value pairs in a file. Successor of Tokyo Cabinet and Kyoto Cabinet

Primary database model

Secondary database models

Time Series DBMS

using the Manticore Columnar Library

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

Score	16.88
Rank	#35	Overall
	#22	Relational DBMS

Score	0.29
Rank	#302	Overall
	#21	Search engines

Score	1.28
Rank	#167	Overall
	#6	Vector DBMS

Score	0.07
Rank	#372	Overall
	#57	Key-value stores

Website

aws.amazon.com/redshift

manticoresearch.com

github.com/qdrant/qdrant
qdrant.tech

dbmx.net/tkrzw

Technical documentation

docs.aws.amazon.com/redshift

manual.manticoresearch.com

qdrant.tech/documentation

Developer

Amazon (based on PostgreSQL)

Manticore Software

Qdrant

Mikio Hirabayashi

Initial release

2012

2017

2021

2020

Current release

6.0, February 2023

0.9.3, August 2020

License

Commercial or Open Source

commercial

Open Source

GPL version 2

Open Source

Apache Version 2.0

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

C++

Rust

C++

Server operating systems

hosted

FreeBSD
Linux
macOS
Windows

Docker
Linux
macOS
Windows

Linux
macOS

Data scheme

yes

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

SQL-like query language

APIs and other access methods

JDBC
ODBC

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

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

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

C++
Java
Python
Ruby

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

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Synchronous replication based on Galera library

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

Immediate 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

using specific database classes

User concepts

Access control

fine grained access rights according to SQL-standard

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.