DBMS > Amazon Redshift vs. Kinetica vs. Percona Server for MongoDB vs. VoltDB

System Properties Comparison Amazon Redshift vs. Kinetica vs. Percona Server for MongoDB vs. VoltDB

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

Fully vectorized database across both GPUs and CPUs

A drop-in replacement for MongoDB Community Edition with enterprise-grade features.

Distributed In-Memory NewSQL RDBMS

Used for OLTP applications with a high frequency of relatively simple transactions, that can hold all their data in memory

Primary database model

Relational DBMS

Document store

Relational DBMS

Secondary database models

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	0.64
Rank	#236	Overall
	#109	Relational DBMS

Score	0.52
Rank	#254	Overall
	#39	Document stores

Score	1.44
Rank	#158	Overall
	#73	Relational DBMS

Website

aws.amazon.com/redshift

www.kinetica.com

www.percona.com/mongodb/software/percona-server-for-mongodb

www.voltdb.com

Technical documentation

docs.aws.amazon.com/redshift

docs.kinetica.com

docs.percona.com/percona-distribution-for-mongodb

docs.voltdb.com

Developer

Amazon (based on PostgreSQL)

Kinetica

Percona

VoltDB Inc.

Initial release

2012

2015

2010

Current release

7.1, August 2021

3.4.10-2.10, November 2017

11.3, April 2022

License

Commercial or Open Source

commercial

Open Source

GPL Version 2

Open Source

AGPL for Community Edition, commercial license for Enterprise, AWS, and Pro Editions

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

C++

Java, C++

Server operating systems

hosted

Linux

Linux
OS X

for development

Data scheme

yes

schema-free

yes

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.

Secondary indexes

restricted

yes

SQL

Support of SQL

yes

does not fully support an SQL-standard

SQL-like DML and DDL statements

yes

only a subset of SQL 99

APIs and other access methods

JDBC
ODBC

JDBC
ODBC
RESTful HTTP API

proprietary protocol using JSON

Java API
JDBC
RESTful HTTP/JSON API

Supported programming languages

All languages supporting JDBC/ODBC

C++
Java
JavaScript (Node.js)
Python

Actionscript
C
C#
C++
Clojure
ColdFusion
D
Dart
Delphi
Erlang
Go
Groovy
Haskell
Java
JavaScript
Lisp
Lua
MatLab
Perl
PHP
PowerShell
Prolog
Python
R
Ruby
Scala
Smalltalk

C#
C++
Erlang

not officially supported
Go
Java
JavaScript

Node.js
PHP
Python

Server-side scripts

Stored procedures

user defined functions

in Python

user defined functions

JavaScript

Java

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

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Source-replica replication

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

Immediate Consistency or Eventual Consistency depending on configuration

Eventual Consistency
Immediate Consistency

Foreign keys

Referential integrity

yes

informational only, not enforced by the system

yes

FOREIGN KEY constraints are not supported

Transaction concepts

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

ACID

Transactions are executed single-threaded within stored procedures

Concurrency

Support for concurrent manipulation of data

yes

Data access is serialized by the server

Durability

Support for making data persistent

yes

Snapshots and command logging

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

via In-Memory Engine

User concepts

Access control

fine grained access rights according to SQL-standard

Access rights for users and roles on table level

Access rights for users and roles

Users and roles with access to stored procedures

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.