DBMS > Amazon Redshift vs. IRONdb vs. Kinetica vs. Qdrant

System Properties Comparison Amazon Redshift vs. IRONdb vs. Kinetica vs. Qdrant

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

IRONdb seems to be discontinued. Therefore it is excluded from the DB-Engines Ranking.

Description

Large scale data warehouse service for use with business intelligence tools

A distributed Time Series DBMS with a focus on scalability, fault tolerance and operational simplicity

Fully vectorized database across both GPUs and CPUs

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

Primary database model

Secondary database models

Spatial DBMS
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.66
Rank	#234	Overall
	#107	Relational DBMS

Score	1.28
Rank	#167	Overall
	#8	Vector DBMS

Website

aws.amazon.com/redshift

www.circonus.com/solutions/time-series-database/

www.kinetica.com

github.com/qdrant/qdrant
qdrant.tech

Technical documentation

docs.aws.amazon.com/redshift

docs.circonus.com/irondb/category/getting-started

docs.kinetica.com

qdrant.tech/documentation

Developer

Amazon (based on PostgreSQL)

Circonus LLC.

Kinetica

Qdrant

Initial release

2012

2017

2012

2021

Current release

V0.10.20, January 2018

7.1, August 2021

License

Commercial or Open Source

commercial

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 and C++

C, C++

Rust

Server operating systems

hosted

Linux

Docker
Linux
macOS
Windows

Data scheme

yes

schema-free

yes

schema-free

Typing

predefined data types such as float or date

yes

text, numeric, histograms

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

SQL

Support of SQL

yes

does not fully support an SQL-standard

SQL-like query language (Circonus Analytics Query Language: CAQL)

SQL-like DML and DDL statements

APIs and other access methods

JDBC
ODBC

HTTP API

JDBC
ODBC
RESTful HTTP API

gRPC
OpenAPI 3.0
RESTful HTTP/JSON API

OpenAPI 3.0

Supported programming languages

All languages supporting JDBC/ODBC

.Net
C
C++
Clojure
Erlang
Go
Haskell
Java
JavaScript
JavaScript (Node.js)
Lisp
Lua
Perl
PHP
Python
R
Ruby
Rust
Scala

C++
Java
JavaScript (Node.js)
Python

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

Server-side scripts

Stored procedures

user defined functions

in Python

yes, in Lua

user defined functions

Triggers

yes

triggers when inserted values for one or more columns fall within a specified range

Partitioning methods

Methods for storing different data on different nodes

Sharding

Automatic, metric affinity per node

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

yes

configurable replication factor, datacenter aware

Source-replica replication

Collection-level replication

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Immediate consistency per node, eventual consistency across nodes

Immediate Consistency or Eventual Consistency depending on configuration

Eventual Consistency, tunable consistency

Foreign keys

Referential integrity

yes

informational only, not enforced by the system

yes

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

In-memory capabilities

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

yes

GPU vRAM or System RAM

yes

User concepts

Access control

fine grained access rights according to SQL-standard

Access rights for users and roles on table level

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.