DBMS > Amazon Redshift vs. Datomic vs. Kyligence Enterprise vs. NSDb vs. Tarantool

System Properties Comparison Amazon Redshift vs. Datomic vs. Kyligence Enterprise vs. NSDb vs. Tarantool

Editorial information provided by DB-Engines

Name

Description

Large scale data warehouse service for use with business intelligence tools

Datomic builds on immutable values, supports point-in-time queries and uses 3rd party systems for durability

A distributed analytics engine for big data, built on top of Apache Kylin

Scalable, High-performance Time Series DBMS designed for Real-time Analytics on top of Kubernetes

In-memory computing platform with a flexible data schema for efficiently building high-performance applications

Primary database model

Relational DBMS

Time Series DBMS

Document store
Key-value store
Relational DBMS

Secondary database models

Spatial DBMS

with Tarantool/GIS extension

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

Score	19.03
Rank	#34	Overall
	#21	Relational DBMS

Score	1.76
Rank	#145	Overall
	#66	Relational DBMS

Score	0.39
Rank	#276	Overall
	#125	Relational DBMS

Score	0.00
Rank	#396	Overall
	#42	Time Series DBMS

Score	1.67
Rank	#150	Overall
	#25	Document stores
	#25	Key-value stores
	#69	Relational DBMS

Website

aws.amazon.com/redshift

www.datomic.com

kyligence.io/kyligence-enterprise

nsdb.io

www.tarantool.io

Technical documentation

docs.aws.amazon.com/redshift

docs.datomic.com

nsdb.io/Architecture

www.tarantool.io/en/doc

Developer

Amazon (based on PostgreSQL)

Cognitect

Kyligence, Inc.

Initial release

2012

2016

2017

2008

Current release

1.0.6735, June 2023

2.10.0, May 2022

License

Commercial or Open Source

commercial

limited edition free

commercial

Open Source

Apache Version 2.0

Open Source

BSD-2, source-available extensions (modules), commercial licenses for Tarantool Enterprise

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, Clojure

Java

Java, Scala

C and C++

Server operating systems

hosted

All OS with a Java VM

Linux

Linux
macOS

BSD
Linux
macOS

Data scheme

yes

Flexible data schema: relational definition for tables with ability to store json-like documents in columns

Typing

predefined data types such as float or date

yes

yes: int, bigint, decimal, string

string, double, decimal, uuid, integer, blob, boolean, datetime

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

all fields are automatically indexed

yes

SQL

Support of SQL

yes

does not fully support an SQL-standard

ANSI SQL for queries (using Apache Calcite)

SQL-like query language

Full-featured ANSI SQL support

APIs and other access methods

JDBC
ODBC

RESTful HTTP API

JDBC
ODBC
RESTful HTTP API

gRPC
HTTP REST
WebSocket

Open binary protocol

Supported programming languages

All languages supporting JDBC/ODBC

Clojure
Java

Java
Scala

C
C#
C++
Erlang
Go
Java
JavaScript
Lua
Perl
PHP
Python
Rust

Server-side scripts

Stored procedures

user defined functions

in Python

yes

Transaction Functions

Lua, C and SQL stored procedures

Triggers

By using transaction functions

yes, before/after data modification events, on replication events, client session events

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

But extensive use of caching in the application peers

Sharding

Sharding, partitioned with virtual buckets by user defined affinity key. Live resharding for scale up and scale down without maintenance downtime.

Replication methods

Methods for redundantly storing data on multiple nodes

yes

none

But extensive use of caching in the application peers

Asynchronous replication with multi-master option
Configurable replication topology (full-mesh, chain, star)
Synchronous quorum replication (with Raft)

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

Casual consistency across sharding partitions
Eventual consistency within replicaset partition

when using asyncronous replication
Immediate Consistency within single instance
Sequential consistency including linearizable read within replicaset partition

when using Raft

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

ACID, with serializable isolation and linearizable read (within partition); Configurable MVCC (within partition); No cross-shard distributed transactions

Concurrency

Support for concurrent manipulation of data

yes

yes, cooperative multitasking

Durability

Support for making data persistent

yes

using external storage systems (e.g. Cassandra, DynamoDB, PostgreSQL, Couchbase and others)

yes

Using Apache Lucene

yes, write ahead logging

In-memory capabilities

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

yes

recommended only for testing and development

yes, full featured in-memory storage engine with persistence

User concepts

Access control

fine grained access rights according to SQL-standard

Access Control Lists
Mutual TLS authentication for Tarantol Enterprise
Password based authentication
Role-based access control (RBAC) and LDAP for Tarantol Enterprise
Users and 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.