DBMS > Amazon Redshift vs. Heroic vs. LokiJS vs. Qdrant

System Properties Comparison Amazon Redshift vs. Heroic vs. LokiJS 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

Time Series DBMS built at Spotify based on Cassandra or Google Cloud Bigtable, and ElasticSearch

In-memory JavaScript DBMS

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

Primary database model

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

Score	17.94
Rank	#34	Overall
	#21	Relational DBMS

Score	0.51
Rank	#255	Overall
	#21	Time Series DBMS

Score	0.43
Rank	#264	Overall
	#42	Document stores

Score	1.16
Rank	#175	Overall
	#6	Vector DBMS

Website

aws.amazon.com/redshift

github.com/spotify/heroic

github.com/techfort/LokiJS

github.com/qdrant/qdrant
qdrant.tech

Technical documentation

docs.aws.amazon.com/redshift

spotify.github.io/heroic

techfort.github.io/LokiJS

qdrant.tech/documentation

Developer

Amazon (based on PostgreSQL)

Spotify

Qdrant

Initial release

2012

2014

2021

License

Commercial or Open Source

commercial

Open Source

Apache 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

Java

JavaScript

Rust

Server operating systems

hosted

server-less, requires a JavaScript environment (browser, Node.js)

Docker
Linux
macOS
Windows

Data scheme

yes

schema-free

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

via Elasticsearch

yes

via views

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

HQL (Heroic Query Language, a JSON-based language)
HTTP API

JavaScript API

gRPC
OpenAPI 3.0
RESTful HTTP/JSON API

OpenAPI 3.0

Supported programming languages

All languages supporting JDBC/ODBC

JavaScript

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

Server-side scripts

Stored procedures

user defined functions

in Python

View functions in JavaScript

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

yes

none

Collection-level replication

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency
Immediate Consistency

none

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

atomic operations within a single collection possible

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

Serialization of a DB in a Node.JS/Cordova/PhoneGap environment. Usage of the IndexedDB-API in a browser.

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

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.