DBMS > Amazon Redshift vs. HEAVY.AI vs. Kinetica vs. LMDB vs. Teradata Aster

System Properties Comparison Amazon Redshift vs. HEAVY.AI vs. Kinetica vs. LMDB vs. Teradata Aster

Editorial information provided by DB-Engines

Name

Teradata Aster has been integrated into other Teradata systems and therefore will be removed from the DB-Engines ranking.

Description

Large scale data warehouse service for use with business intelligence tools

A high performance, column-oriented RDBMS, specifically developed to harness the massive parallelism of modern CPU and GPU hardware

Fully vectorized database across both GPUs and CPUs

A high performant, light-weight, embedded key-value database library

Platform for big data analytics on multistructured data sources and types

Primary database model

Relational DBMS

Key-value store

Relational DBMS

Secondary database models

Spatial DBMS

Spatial DBMS
Time Series DBMS

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

Score	17.94
Rank	#34	Overall
	#21	Relational DBMS

Score	1.77
Rank	#141	Overall
	#65	Relational DBMS

Score	0.64
Rank	#236	Overall
	#109	Relational DBMS

Score	1.99
Rank	#125	Overall
	#21	Key-value stores

Website

aws.amazon.com/redshift

github.com/heavyai/heavydb
www.heavy.ai

www.kinetica.com

www.symas.com/symas-embedded-database-lmdb

Technical documentation

docs.aws.amazon.com/redshift

docs.heavy.ai

docs.kinetica.com

www.lmdb.tech/doc

Developer

Amazon (based on PostgreSQL)

HEAVY.AI, Inc.

Kinetica

Symas

Teradata

Initial release

2012

2016

2012

2011

2005

Current release

5.10, January 2022

7.1, August 2021

0.9.32, January 2024

License

Commercial or Open Source

commercial

Open Source

Apache Version 2; enterprise edition available

commercial

Open Source

commercial

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 CUDA

C, C++

Server operating systems

hosted

Linux

Linux
Unix
Windows

Linux

Data scheme

yes

schema-free

Flexible Schema (defined schema, partial schema, schema free)

defined schema within the relational store; partial schema or schema free in the Aster File Store

Typing

predefined data types such as float or date

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.

yes

in Aster File Store

Secondary indexes

restricted

yes

SQL

Support of SQL

yes

does not fully support an SQL-standard

yes

SQL-like DML and DDL statements

yes

APIs and other access methods

JDBC
ODBC

JDBC
ODBC
Thrift
Vega

JDBC
ODBC
RESTful HTTP API

ADO.NET
JDBC
ODBC
OLE DB

Supported programming languages

All languages supporting JDBC/ODBC

All languages supporting JDBC/ODBC/Thrift
Python

C++
Java
JavaScript (Node.js)
Python

.Net
C
C++
Clojure
Go
Haskell
Java
JavaScript (Node.js)
Lisp
Lua
MatLab
Nim
Objective C
OCaml
Perl
PHP
Python
R
Ruby
Rust
Swift
Tcl

C
C#
C++
Java
Python
R

Server-side scripts

Stored procedures

user defined functions

in Python

user defined functions

R packages

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

Round robin

Sharding

none

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Multi-source replication

Source-replica replication

none

yes

Dimension tables are replicated across all nodes in the cluster. The number of replicas for the file store can be configured.

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

SQL Map-Reduce Framework

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Immediate Consistency or Eventual Consistency depending on configuration

Immediate Consistency

Immediate Consistency or Eventual Consistency depending on configuration

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

fine grained access rights according to SQL-standard

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.