DBMS > Amazon Redshift vs. Heroic vs. LokiJS vs. SiriDB vs. Vitess

System Properties Comparison Amazon Redshift vs. Heroic vs. LokiJS vs. SiriDB vs. Vitess

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

Open Source Time Series DBMS

Scalable, distributed, cloud-native DBMS, extending MySQL

Primary database model

Secondary database models

Document store
Spatial DBMS

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	0.00
Rank	#383	Overall
	#41	Time Series DBMS

Score	0.82
Rank	#209	Overall
	#97	Relational DBMS

Website

aws.amazon.com/redshift

github.com/spotify/heroic

github.com/techfort/LokiJS

siridb.com

vitess.io

Technical documentation

docs.aws.amazon.com/redshift

spotify.github.io/heroic

techfort.github.io/LokiJS

docs.siridb.com

vitess.io/docs

Developer

Amazon (based on PostgreSQL)

Spotify

Cesbit

The Linux Foundation, PlanetScale

Initial release

2012

2014

2017

2013

Current release

15.0.2, December 2022

License

Commercial or Open Source

commercial

Open Source

Apache 2.0

Open Source

MIT License

Open Source

Apache Version 2.0, commercial licenses available

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

Server operating systems

hosted

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

Linux

Docker
Linux
macOS

Data scheme

yes

schema-free

yes

Typing

predefined data types such as float or date

yes

Numeric data

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

via Elasticsearch

yes

via views

yes

SQL

Support of SQL

yes

does not fully support an SQL-standard

yes

with proprietary extensions

APIs and other access methods

JDBC
ODBC

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

JavaScript API

HTTP API

ADO.NET
JDBC
MySQL protocol
ODBC

Supported programming languages

All languages supporting JDBC/ODBC

JavaScript

C
C++
Go
Java
JavaScript (Node.js)
PHP
Python
R

Ada
C
C#
C++
D
Delphi
Eiffel
Erlang
Haskell
Java
JavaScript (Node.js)
Objective-C
OCaml
Perl
PHP
Python
Ruby
Scheme
Tcl

Server-side scripts

Stored procedures

user defined functions

in Python

View functions in JavaScript

yes

proprietary syntax

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

yes

Multi-source replication
Source-replica 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 across shards
Immediate Consistency within a shard

Foreign keys

Referential integrity

yes

informational only, not enforced by the system

yes

not for MyISAM storage engine

Transaction concepts

Support to ensure data integrity after non-atomic manipulations of data

ACID

atomic operations within a single collection possible

ACID at shard level

Concurrency

Support for concurrent manipulation of data

yes

table locks or row locks depending on storage engine

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

simple rights management via user accounts

Users with fine-grained authorization concept

no user groups or roles

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.