DBMS > Amazon Redshift vs. Microsoft Azure Table Storage vs. Tarantool vs. UniData,UniVerse

System Properties Comparison Amazon Redshift vs. Microsoft Azure Table Storage vs. Tarantool vs. UniData,UniVerse

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

A Wide Column Store for rapid development using massive semi-structured datasets

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

MultiValue database and application server with SQL mapping layer and meta database capabilities

Primary database model

Relational DBMS

Wide column store

Document store
Key-value store
Relational DBMS

Multivalue DBMS

Secondary database models

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	4.04
Rank	#77	Overall
	#6	Wide column stores

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

Score	2.85
Rank	#98	Overall
	#1	Multivalue DBMS

Website

aws.amazon.com/redshift

azure.microsoft.com/en-us/services/storage/tables

www.tarantool.io

www.rocketsoftware.com/products/rocket-multivalue-application-development-platform/rocket-unidata

Technical documentation

docs.aws.amazon.com/redshift

www.tarantool.io/en/doc

docs.rocketsoftware.com/bundle?cluster=true&labelkey=unidata&labelkey=prod_unidata

Developer

Amazon (based on PostgreSQL)

Microsoft

Rocket Software

Initial release

2012

2008

1985

Current release

2.10.0, May 2022

License

Commercial or Open Source

commercial

Open Source

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

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

Server operating systems

hosted

BSD
Linux
macOS

AIX
HP-UX
Linux
Solaris
Windows

Data scheme

yes

schema-free

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

schema-free

Typing

predefined data types such as float or date

yes

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

optional

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

Full-featured ANSI SQL support

yes

APIs and other access methods

JDBC
ODBC

RESTful HTTP API

Open binary protocol

Java API

JPA
JDBC
ODBC
OLE DB
Proprietary protocol
RESTful HTTP API
SOAP-based API

Supported programming languages

All languages supporting JDBC/ODBC

.Net
C#
C++
Java
JavaScript (Node.js)
PHP
Python
Ruby

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

.Net
Basic

U2 Basic
C
Java

Server-side scripts

Stored procedures

user defined functions

in Python

Lua, C and SQL stored procedures

yes

Triggers

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

yes

U2 Basic

Partitioning methods

Methods for storing different data on different nodes

Sharding

Implicit feature of the cloud service

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

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes

implicit feature of the cloud service. Replication either local, cross-facility or geo-redundant.

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

Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate 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

optimistic locking

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

ACID

configurable

Concurrency

Support for concurrent manipulation of data

yes

yes, cooperative multitasking

yes

Durability

Support for making data persistent

yes

yes, write ahead logging

yes

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

User concepts

Access control

fine grained access rights according to SQL-standard

Access rights based on private key authentication or shared access signatures

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

Access rights according to SQL-standard and operating system based

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.