DBMS > Amazon Redshift vs. Graph Engine vs. Qdrant vs. TerarkDB vs. Warp 10

System Properties Comparison Amazon Redshift vs. Graph Engine vs. Qdrant vs. TerarkDB vs. Warp 10

Editorial information provided by DB-Engines

Name

Description

Large scale data warehouse service for use with business intelligence tools

A distributed in-memory data processing engine, underpinned by a strongly-typed RAM store and a general distributed computation engine

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

A key-value store forked from RocksDB with advanced compression algorithms. It can be used standalone or as a storage engine for MySQL and MongoDB

TimeSeries DBMS specialized on timestamped geo data based on LevelDB or HBase

Primary database model

Relational DBMS

Graph DBMS
Key-value store

Vector DBMS

Key-value store

Time Series DBMS

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

Score	16.88
Rank	#35	Overall
	#22	Relational DBMS

Score	0.67
Rank	#232	Overall
	#21	Graph DBMS
	#34	Key-value stores

Score	1.28
Rank	#167	Overall
	#7	Vector DBMS

Score	0.08
Rank	#367	Overall
	#56	Key-value stores

Score	0.14
Rank	#344	Overall
	#32	Time Series DBMS

Website

aws.amazon.com/redshift

www.graphengine.io

github.com/qdrant/qdrant
qdrant.tech

github.com/bytedance/terarkdb

www.warp10.io

Technical documentation

docs.aws.amazon.com/redshift

www.graphengine.io/docs/manual

qdrant.tech/documentation

bytedance.larkoffice.com/docs/doccnZmYFqHBm06BbvYgjsHHcKc

www.warp10.io/content/02_Getting_started

Developer

Amazon (based on PostgreSQL)

Microsoft

Qdrant

ByteDance, originally Terark

SenX

Initial release

2012

2010

2021

2016

2015

License

Commercial or Open Source

commercial

Open Source

MIT License

Open Source

Apache Version 2.0

commercial

restricted open source version available

Open Source

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

.NET and C

Rust

C++

Java

Server operating systems

hosted

.NET

Docker
Linux
macOS
Windows

Linux
OS X
Windows

Data scheme

yes

schema-free

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

SQL

Support of SQL

yes

does not fully support an SQL-standard

APIs and other access methods

JDBC
ODBC

RESTful HTTP API

gRPC
OpenAPI 3.0
RESTful HTTP/JSON API

OpenAPI 3.0

C++ API
Java API

HTTP API
Jupyter
WebSocket

Supported programming languages

All languages supporting JDBC/ODBC

C#
C++
F#
Visual Basic

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

C++
Java

Server-side scripts

Stored procedures

user defined functions

in Python

yes

WarpScript

Triggers

Partitioning methods

Methods for storing different data on different nodes

Sharding

horizontal partitioning

Sharding

none

Sharding

based on HBase

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Collection-level replication

none

selectable replication factor

based on HBase

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

based on HBase

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

optional: either by committing a write-ahead log (WAL) to the local persistent storage or by dumping the memory to a persistent storage

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

Key-based authentication

Mandatory use of cryptographic tokens, containing fine-grained authorizations

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.