DBMS > Amazon Redshift vs. Cassandra vs. Tarantool vs. Valentina Server vs. VoltDB

System Properties Comparison Amazon Redshift vs. Cassandra vs. Tarantool vs. Valentina Server vs. VoltDB

Editorial information provided by DB-Engines

Name

Description

Large scale data warehouse service for use with business intelligence tools

Wide-column store based on ideas of BigTable and DynamoDB

Optimized for write access

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

Object-relational database and reports server

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

Wide column store

Document store
Key-value store
Relational DBMS

Relational DBMS

Secondary database models

Vector DBMS

starting with release V5

Spatial DBMS

with Tarantool/GIS extension

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

Score	16.88
Rank	#35	Overall
	#22	Relational DBMS

Score	98.83
Rank	#12	Overall
	#1	Wide column stores

Score	1.67
Rank	#143	Overall
	#25	Document stores
	#25	Key-value stores
	#65	Relational DBMS

Score	0.21
Rank	#325	Overall
	#144	Relational DBMS

Score	1.47
Rank	#157	Overall
	#73	Relational DBMS

Website

aws.amazon.com/redshift

Technical documentation

docs.aws.amazon.com/redshift

cassandra.apache.org/doc/latest

www.tarantool.io/en/doc

valentina-db.com/docs/dokuwiki/v5/doku.php

docs.voltdb.com

Developer

Amazon (based on PostgreSQL)

Apache Software Foundation

Apache top level project, originally developped by Facebook

Paradigma Software

VoltDB Inc.

Initial release

2012

2008

1999

2010

Current release

4.1.3, July 2023

2.10.0, May 2022

5.7.5

11.3, April 2022

License

Commercial or Open Source

commercial

Open Source

Apache version 2

Open Source

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

commercial

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.

Astra DB: Multi-cloud DBaaS built on Apache Cassandra.

Implementation language

Java

C and C++

Java, C++

Server operating systems

hosted

BSD
Linux
OS X
Windows

BSD
Linux
macOS

Linux
OS X
Windows

Linux
OS X

for development

Data scheme

yes

schema-free

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

yes

Typing

predefined data types such as float or date

yes

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

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

only equality queries, not always the best performing solution

yes

SQL

Support of SQL

yes

does not fully support an SQL-standard

SQL-like SELECT, DML and DDL statements (CQL)

Full-featured ANSI SQL support

yes

only a subset of SQL 99

APIs and other access methods

JDBC
ODBC

Proprietary protocol

CQL (Cassandra Query Language, an SQL-like language)
Thrift

Open binary protocol

ODBC

Java API
JDBC
RESTful HTTP/JSON API

Supported programming languages

All languages supporting JDBC/ODBC

C#
C++
Clojure
Erlang
Go
Haskell
Java
JavaScript

Node.js
Perl
PHP
Python
Ruby
Scala

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

.Net
C
C#
C++
Objective-C
PHP
Ruby
Visual Basic
Visual Basic.NET

C#
C++
Erlang

not officially supported
Go
Java
JavaScript

Node.js
PHP
Python

Server-side scripts

Stored procedures

user defined functions

in Python

Lua, C and SQL stored procedures

yes

Java

Triggers

yes

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

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

no "single point of failure"

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

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

yes

selectable replication factor

Representation of geographical distribution of servers is possible

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

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

can be individually decided for each write operation

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

FOREIGN KEY constraints are not supported

Transaction concepts

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

ACID

Atomicity and isolation are supported for single operations

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

ACID

Transactions are executed single-threaded within stored procedures

Concurrency

Support for concurrent manipulation of data

yes

yes, cooperative multitasking

yes

Data access is serialized by the server

Durability

Support for making data persistent

yes

yes, write ahead logging

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

yes, full featured in-memory storage engine with persistence

yes

User concepts

Access control

fine grained access rights according to SQL-standard

Access rights for users can be defined per object

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

fine grained access rights according to SQL-standard

Users and roles with access to stored procedures

More information provided by the system vendor

Specific characteristics

Apache Cassandra is the leading NoSQL, distributed database management system, well...
» more

Competitive advantages

No single point of failure ensures 100% availability . Operational simplicity for...
» more

Typical application scenarios

Internet of Things (IOT), fraud detection applications, recommendation engines, product...
» more

Key customers

Apple, Netflix, Uber, ING,, Intuit,Fidelity, NY Times, Outbrain, BazaarVoice, Best...
» more

Market metrics

Cassandra is used by 40% of the Fortune 100.
» more

Licensing and pricing models

Apache licenseÂ Pricing for commercial distributions provided by DataStax and available...
» more

News

Introducing Tejas Kumar, Developer Relations Engineer
7 June 2024

Indexing All of Wikipedia on a Laptop
5 June 2024

An Introduction to Phil Nash, Developer Relations
3 June 2024

Focus on Creativity, Not Clusters: DataStax Mission Control in Action!
30 May 2024

How Concide Built its Chat Platform with Enhanced Document Management for Legal Tech Professionals
23 May 2024

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.